Handling of Inactive Parameters Upon Release and Re-Suspend

ABSTRACT

Systems and methods are disclosed herein for updating stored User Equipment (UE) context information upon re-suspend of the UE in response to a resume request from the UE. In some embodiments, a method in a UE comprises transmitting a Radio Resource Control (RRC) resume request message and, in response to the RRC resume request message, receiving an RRC connection release message with an indication for suspend. The method further comprises, in response to receiving the RRC connection release message with an indication for suspend, replacing information in a stored Access Stratum (AS) context of the UE with new information.

RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 17/409,662 filed Aug. 23, 2021, which is acontinuation application of U.S. patent application Ser. No. 16/657,296,filed Oct. 18, 2019, granted as U.S. Pat. No. 11,116,031 on Sep. 7,2021, which is a continuation application of U.S. patent applicationSer. No. 16/386,148, filed Apr. 16, 2019, granted as U.S. Pat. No.10,485,051 on Nov. 19, 2019, which claims the benefit of provisionalpatent application Ser. No. 62/657,974, filed Apr. 16, 2018, thedisclosure of which are hereby incorporated herein by reference in theirentirety.

TECHNICAL FIELD

The present disclosure relates to connection resume/suspend in awireless communication system.

BACKGROUND

In Long Term Evolution (LTE) Release 13 a mechanism was introduced forthe User Equipment (UE) to be suspended by the network. This suspendedstate is similar to RRC_IDLE. However, unlike the RRC_IDLE state, the UEstores the Access Stratum (AS) context or Radio Resource Control (RRC)context. This makes it possible to reduce the signaling when the UE isbecoming active again by resuming the RRC connection, instead ofestablishing the RRC connection from scratch, as in prior releases.Reducing the signaling may have several benefits such as reducinglatency (e.g. for smart phones accessing the Internet) and/or reducingsignaling leads such that battery consumption is reduced for machinetype devices sending very little data.

The Release 13 solution is based on the UE sending anRRCConnectionResumeRequest message to the network and receiving anRRCConnectionResume message from the network in response. TheRRCConnectionResume message is not encrypted but integrity protected.

As part of the standardized work on Fifth Generation (5G) New Radio (NR)in the Third Generation Partnership Project (3GPP), it has been decidedthat NR should support an RRC_INACTIVE state with similar properties asthe suspended state in LTE Release 13. The RRC_INACTIVE has slightlydifferent properties from the suspended state in that it is a separateRRC state and not part of RRC_IDLE as in LTE. Additionally the CoreNetwork (CN)/Radio Access Network (RAN) connection (Next Generation (NG)or N2 interface) is kept for RRC_INACTIVE, whereas it was suspended inLTE.

FIG. 1 illustrates possible UE state transitions in NR. The propertiesof the states illustrated in FIG. 1 are as follows:

-   -   RRC_IDLE:        -   A UE specific Discontinuous Reception (DRX) may be            configured by upper layers;        -   UE controlled mobility based on network configuration;        -   The UE:            -   Monitors a Paging channel for CN paging using 5G System                Architecture Evolution (SAE) Temporary Mobile Subscriber                Identity (TMSI) (5G-S-TMSI);            -   Performs neighboring cell measurements and cell                (re-)selection;            -   Acquires system information.    -   RRC_INACTIVE:        -   A UE specific DRX may be configured by upper layers or by            RRC layer;        -   UE controlled mobility based on network configuration;        -   The UE stores the AS context;        -   The UE:            -   Monitors a Paging channel for CN paging using 5G-S-TMSI                and RAN paging using Inactive Radio Network Temporary                Identifier (I-RNTI);            -   Performs neighboring cell measurements and cell                (re-)selection;            -   Performs RAN-based notification area updates                periodically and when moving outside the RAN-based                notification area;            -   Acquires system information.    -   RRC_CONNECTED:        -   The UE stores the AS context;        -   Transfer of unicast data to/from UE;        -   At lower layers, the UE may be configured with a UE specific            DRX;        -   For UEs supporting Carrier Aggregation (CA), use of one or            more Secondary Cells (SCells), aggregated with the Special            Cell (SpCell), for increased bandwidth;        -   For UEs supporting Dual Connectivity (DC), use of one            Secondary Cell Group (SCG), aggregated with the Master Cell            Group (MCG), for increased bandwidth;        -   Network controlled mobility, i.e. handover within NR and            to/from Evolved Universal Mobile Telecommunications Service            (UMTS) Terrestrial RAN (E-UTRAN);        -   The UE:            -   Monitors a Paging channel;            -   Monitors control channels associated with the shared                data channel to determine if data is scheduled for it;            -   Provides channel quality and feedback information;            -   Performs neighboring cell measurements and measurement                reporting;            -   Acquires system information.

In LTE, an RRC_CONNECTED UE can be suspended by receiving anRRCConnectionRelease message with a suspend indicator. Upon receivingthat message, the UE stores some parameters and deletes others. Some ofthese stored parameters, provided by the source node that is suspendingthe UE, are used by the UE when the UE attempts to resume theconnection.

More particularly, upon receiving an indication to be suspended, the UEstores the AS context including the RRC configuration used inRRC_CONNECTED and the following parameters associated with the lastsource Primary Cell (PCell) the UE was connected to when the UE was inRRC_CONNECTED:

-   -   Cell Radio Network Temporary Identifier (C-RNTI) of the last        PCell in RRC_CONNECTED;    -   Cell Identity (28 bits value that identifies a cell within a        Public Land Mobile Network (PLMN)) of the last PCell in        RRC_CONNECTED;    -   Physical Cell Identity (PCI) of the last PCell in RRC_CONNECTED.

Further details relating to how the UE behaves according to the LTEstandard in response to receiving an RRCConnectionRelease message arefound in Appendix A.

When the RRC_IDLE UE with suspend configuration wants to resume (i.e.,in LTE), the stored parameters (C-RNTI, Cell Identity, and PCI)associated with the last PCell the UE was connected to when the UE wasin RRC_CONNECTED are used in the RRC Resume procedure to compute theshort Message Authentication Code for Integrity (MAC-I) security tokenso that the UE can be recognized by the source node hosting the UE AScontext. This enables the source node to accept a context fetch requestfrom the target node. Further details relating this procedure may befound in Appendix B.

There currently exist certain challenge(s). In NR RRC, which isdifferent from LTE RRC, the network may respond to a ResumeRequest fromthe UE with a Suspend message (or equivalent, such as a Release messagewith a suspend indication or configuration) which immediately orders theUE back to RRC_INACTIVE state. LTE does not permit sending a suspendmessage (e.g., a release message with a suspend indication) directly tothe UE trying to resume the connection, as in the example shown in FIG.2 . Rather, this feature is new in NR.

In NR RRC, the network may alternatively respond to a ResumeRequest fromthe UE with a Release message (i.e., without a suspend indication) whichimmediately orders the UE back to RRC_IDLE state. This message isencrypted. LTE does not permit sending a release message directly to theUE trying to resume the connection, as in the example shown in FIG. 3 .Rather, this feature is also new in NR.

Currently known procedures for RRC connection handling (e.g., in NRdraft specifications) adopt features similar to LTE. However, RRCconnection handling when a UE is re-suspended are not well developed orunderstood.

SUMMARY

Systems and methods are disclosed herein for updating stored UserEquipment (UE) context information upon re-suspend of the UE in responseto a resume request from the UE. In some embodiments, a method in a UEcomprises transmitting a Radio Resource Control (RRC) resume requestmessage and, in response to the RRC resume request message, receiving anRRC connection release message with an indication for suspend. Themethod further comprises, in response to receiving the RRC connectionrelease message with an indication for suspend, replacing information ina stored Access Stratum (AS) context of the UE with new information.Replacing the information in the stored AS context of the UE comprises:replacing stored security context information with security contextinformation comprised in the RRC connection release message; replacing astored Inactive Radio Network Temporary Identifier (I-RNTI) with anI-RNTI comprised in the RRC connection release message; replacing astored cell identity with a cell identity of a cell in which the UE sentthe RRC resume request message and received the RRC connection releasemessage; replacing a stored Physical Cell Identity (PCI) with a PCI ofthe cell in which the UE sent the RRC resume request message andreceived the RRC connection release message; or replacing a stored CellRadio Network Temporary Identifier (C-RNTI) with a C-RNTI obtained bythe UE for the cell in which the UE sent the RRC resume request messageand received the RRC connection release message. In this manner, thestored AS context of the UE is updated upon re-suspend of the UE.

In some embodiments, the method further comprises determining that theRRC connection release message comprises security context information,and replacing the information in the stored AS context of the UEcomprises replacing the stored security context information with thesecurity context information comprised in the RRC connection releasemessage.

In some embodiments, the method further comprises determining that theRRC connection release message comprises an I-RNTI, and replacing theinformation in the stored AS context of the UE comprises replacing thestored I-RNTI with the I-RNTI comprised in the RRC connection releasemessage.

In some embodiments, the method further comprises obtaining the cellidentity of the cell prior to sending the RRC resume request message,and replacing the information in the stored AS context of the UEcomprises replacing the stored cell identity with the cell identity ofthe cell in which the UE sent the RRC resume request message andreceived the RRC connection release message.

In some embodiments, the method further comprises obtaining the PCI ofthe cell prior to sending the RRC resume request message, and replacingthe information in the stored AS context of the UE comprises replacingthe stored PCI with the PCI of the cell in which the UE sent the RRCresume request message and received the RRC connection release message.

In some embodiments, the method further comprises obtaining the C-RNTIfor the cell prior to sending the RRC resume request message, andreplacing the information in the stored AS context of the UE comprisesreplacing the stored C-RNTI with the C-RNTI obtained by the UE for thecell in which the UE sent the RRC resume request message and receivedthe RRC connection release message.

In some embodiments, the C-RNTI obtained by the UE for the cell in whichthe UE sent the RRC resume request message and received the RRCconnection release message is a temporary C-RNTI.

In some embodiments, the method further comprises, after replacing theinformation in the stored AS context of the UE to provide an updated AScontext of the UE, using the updated AS context of the UE to send asubsequent RRC resume request. In some embodiments, using the updated AScontext of the UE to send the subsequent RRC resume request comprisesusing the updated AS context to calculate a security integrity tokencomprised in the subsequent RRC resume request.

Embodiments of a UE are also disclosed. In some embodiments, a UE isadapted to transmit a RRC resume request message and, in response to theRRC resume request message, receive an RRC connection release messagewith an indication for suspend. The UE is further adapted to, inresponse to receiving the RRC connection release message with anindication for suspend, replace information in a stored AS context ofthe UE with new information. In order to replace the information in thestored AS context of the UE, the UE is further adapted to: replacestored security context information with security context informationcomprised in the RRC connection release message; replace a stored I-RNTIwith an I-RNTI comprised in the RRC connection release message; replacea stored cell identity with a cell identity of a cell in which the UEsent the RRC resume request message and received the RRC connectionrelease message; replace a stored PCI with a PCI of the cell in whichthe UE sent the RRC resume request message and received the RRCconnection release message; or replace a stored C-RNTI with a C-RNTIobtained by the UE for the cell in which the UE sent the RRC resumerequest message and received the RRC connection release message.

In some other embodiments, a UE comprises a radio interface andprocessing circuitry associated with the radio interface. The processingcircuitry is configured to cause the UE to transmit a RRC resume requestmessage and, in response to the RRC resume request message, receive anRRC connection release message with an indication for suspend. Theprocessing circuitry is further configured to cause the UE to, inresponse to receiving the RRC connection release message with anindication for suspend, replace information in a stored AS context ofthe UE with new information. In order to replace the information in thestored AS context of the UE, the processing circuitry is furtherconfigured to cause the UE to: replace stored security contextinformation with security context information comprised in the RRCconnection release message; replace a stored I-RNTI with an I-RNTIcomprised in the RRC connection release message; replace a stored cellidentity with a cell identity of a cell in which the UE sent the RRCresume request message and received the RRC connection release message;replace a stored PCI with a PCI of the cell in which the UE sent the RRCresume request message and received the RRC connection release message;or replace a stored C-RNTI with a C-RNTI obtained by the UE for the cellin which the UE sent the RRC resume request message and received the RRCconnection release message.

Embodiments of a method in a network node are also disclosed. In someembodiments, a method in network node for updating a UE AS contextstored for a UE upon re-suspending the UE in response to a RRC resumerequest from the UE comprises receiving, from a UE, a RRC resume requestmessage and, in response to receiving the RRC resume request message,transmitting, to the UE, an RRC connection release message with anindication for suspend. The method further comprises, in response totransmitting the RRC connection release message with an indication forsuspend, replacing information in a stored AS context of the UE with newinformation. Replacing the information in the stored AS context of theUE comprises: replacing stored security context information withsecurity context information comprised in the RRC connection releasemessage; replacing a stored I-RNTI with an I-RNTI comprised in the RRCconnection release message; replacing a stored cell identity with a cellidentity of a cell in which the UE sent the RRC resume request messageand received the RRC connection release message; replacing a stored PCIwith a PCI of the cell in which the UE sent the RRC resume requestmessage and received the RRC connection release message; or replacing astored C-RNTI with a C-RNTI obtained by the UE for the cell in which theUE sent the RRC resume request message and received the RRC connectionrelease message.

In some embodiments, replacing the information in the stored AS contextof the UE comprises replacing the stored security context informationwith the security context information comprised in the RRC connectionrelease message.

In some embodiments, replacing the information in the stored AS contextof the UE comprises replacing the stored I-RNTI with the I-RNTIcomprised in the RRC connection release message.

In some embodiments, replacing the information in the stored AS contextof the UE comprises replacing the stored cell identity with the cellidentity of the cell in which the UE sent the RRC resume request messageand received the RRC connection release message.

In some embodiments, replacing the information in the stored AS contextof the UE comprises replacing the stored PCI with the PCI of the cell inwhich the UE sent the RRC resume request message and received the RRCconnection release message.

In some embodiments, replacing the information in the stored AS contextof the UE comprises replacing the stored C-RNTI with the C-RNTI obtainedby the UE for the cell in which the UE sent the RRC resume requestmessage and received the RRC connection release message.

Embodiments of a network node are also disclosed. In some embodiments, anetwork node for updating a UE AS context stored for a UE uponre-suspending the UE in response to a RRC resume request from the UE isadapted to receive, from a UE, a RRC resume request message and, inresponse to receiving the RRC resume request message, transmit, to theUE, an RRC connection release message with an indication for suspend.The network node is further adapted to, in response to transmitting theRRC connection release message with an indication for suspend, replaceinformation in a stored AS context of the UE with new information. Inorder to replace the information in the stored AS context of the UE, thenetwork node is further adapted to: replace stored security contextinformation with security context information comprised in the RRCconnection release message; replace a stored I-RNTI with an I-RNTIcomprised in the RRC connection release message; replace a stored cellidentity with a cell identity of a cell in which the UE sent the RRCresume request message and received the RRC connection release message;replace a stored PCI with a PCI of the cell in which the UE sent the RRCresume request message and received the RRC connection release message;or replace a stored C-RNTI with a C-RNTI obtained by the UE for the cellin which the UE sent the RRC resume request message and received the RRCconnection release message.

In some embodiments, a network node for updating a UE AS context storedfor a UE upon re-suspending the UE in response to a RRC resume requestfrom the UE comprises processing circuitry configured to cause thenetwork node to receive, from a UE, a RRC resume request message and, inresponse to receiving the RRC resume request message, transmit, to theUE, an RRC connection release message with an indication for suspend.The processing circuitry is further configured to cause the network nodeto, in response to transmitting the RRC connection release message withan indication for suspend, replace information in a stored AS context ofthe UE with new information. In order to replace the information in thestored AS context of the UE, the processing circuitry is furtherconfigured to cause the network node to: replace stored security contextinformation with security context information comprised in the RRCconnection release message; replace a stored I-RNTI with an I-RNTIcomprised in the RRC connection release message; replace a stored cellidentity with a cell identity of a cell in which the UE sent the RRCresume request message and received the RRC connection release message;replace a stored PCI with a PCI of the cell in which the UE sent the RRCresume request message and received the RRC connection release message;or replace a stored C-RNTI with a C-RNTI obtained by the UE for the cellin which the UE sent the RRC resume request message and received the RRCconnection release message.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawing figures incorporated in and forming a part ofthis specification illustrate several aspects of the disclosure, andtogether with the description serve to explain the principles of thedisclosure.

FIG. 1 illustrates possible User Equipment (UE) state transitions in NewRadio (NR);

FIG. 2 illustrates the sending of a suspend message directly to a UEtrying to resume its connection;

FIG. 3 illustrates the sending of a release message directly to a UEtrying to resume its connection;

FIG. 4 illustrates an example wireless communication network, accordingto one or more embodiments;

FIG. 5 illustrates an example of the basic NR physical resourcerepresented as a time-frequency grid;

FIG. 6 illustrates an example time-domain structure for NR;

FIG. 7 depicts a method implemented in a wireless device (e.g., UE) inaccordance with particular embodiments;

FIG. 8 depicts a method implemented in a base station in accordance withparticular embodiments;

FIG. 9 illustrates one example embodiment of a wireless device;

FIG. 10 illustrates another example embodiment of a wireless device;

FIG. 11 illustrates one example embodiment of a base station;

FIG. 12 illustrates another example embodiment of a base station;

FIG. 13 illustrates the operation of a UE and a base station to refresha stored Access Stratum (AS) context of the UE upon re-suspend of the UEin response to a resume request from the UE in accordance with someembodiments of the present disclosure;

FIG. 14 illustrates an exemplary wireless network according to someembodiments disclosed herein;

FIG. 15 illustrates one embodiment of a UE according to some embodimentsdisclosed herein;

FIG. 16 is a schematic block diagram illustrating a virtualizationenvironment in which functions implemented by some embodiments may bevirtualized;

FIG. 17 illustrates a communication system including a telecommunicationnetwork according to some embodiments disclosed herein;

FIG. 18 illustrates a communication system according to some embodimentsdisclosed herein;

FIG. 19 is a flowchart illustrating a method implemented in acommunication system according to some embodiments disclosed herein;

FIG. 20 is a flowchart illustrating a method implemented in acommunication system according to some embodiments disclosed herein;

FIG. 21 is a flowchart illustrating a method implemented in acommunication system according to some embodiments disclosed herein; and

FIG. 22 is a flowchart illustrating a method implemented in acommunication system according to some embodiments disclosed herein.

DETAILED DESCRIPTION

The embodiments set forth below represent information to enable thoseskilled in the art to practice the embodiments and illustrate the bestmode of practicing the embodiments. Upon reading the followingdescription in light of the accompanying drawing figures, those skilledin the art will understand the concepts of the disclosure and willrecognize applications of these concepts not particularly addressedherein. It should be understood that these concepts and applicationsfall within the scope of the disclosure.

As discussed in the Background section, currently known procedures forRadio Resource Control (RRC) connection handling (e.g., in New Radio(NR) draft specifications) adopt features similar to those in Long TermEvolution (LTE). However, RRC connection handling when a User Equipment(UE) is re-suspended are not well developed or understood. Details onone approach to re-suspending a UE may be found in Appendix C.

One approach that may be appropriate in NR is for the UE to derive newsecurity keys (KgNB, Krrcint, etc.) prior to sending theRRCResumeRequest message. These keys may be used to calculate thesecurity token used in the RRCResumeRequest message and used to encryptand integrity protect the response message (RRCSuspend, RRCRelease,RRCResume). An example of such an approach may be found in Appendix D.

In the above discussed approaches, the UE does not store the UE AccessStratum (AS) Context including the current RRC configuration, thecurrent security context, the Packet Data Convergence Protocol (PDCP)state including Robust Header Compression (ROHC) state, Cell RadioNetwork Temporary Identifier (C-RNTI) used in the source Primary Cell(PCell), the cellIdentity, and the Physical Cell Identity (PCI) of thesource PCell in case it is receiving the RRCSuspend in response to anRRCResumeRequest. The assumption here is that the UE should use the oldstored context the next time it sends an RRCResumeRequest.

This approach is less secure since the old security context (e.g.security keys) need to be reused to derive new security keys, ratherthan using the fresh UE security keys which were generated beforesending the RRCResumeRequest as the base keys for generating newsecurity keys. Moreover, this approach also requires the network tostore the old security context when it sends a RRCSuspend to the UE, tobe used at the next attempt. Additionally the network needs to maintainmore parameters which are related to the old node or cell for which theUE was last in Connected state such as C-RNTI in the old source PCell(i.e., the PCell in which the UE received the previous RRCSuspend),cellIdentity of the source PCell, and the PCI of the source PCell. Theseparameters would most likely be different from the ones used in thetarget node (i.e., the node to which the UE sends the RRCResumeRequest).

Using the old parameter as input to future RRCResumeRequest couldintroduce security issues as the usage of location dependent parametersto compute the integrity token in LTE is a strength of the LTE securitysolution for RRC Resume. However, with the above discussed NR approach,this principle is broken and, although the UE could be moving around andpossibly updating its security parameters and the ones that are locationdependent, the UE would keep using old parameters.

In addition, it is unclear what the UE would do upon receivingRRCRelease. For example, the UE may update these location dependentparameters or not. Moreover, although the UE may store some parameters,it is unclear what should happen if these parameters are already stored.

For example, with respect to the parameters resumeIdentity,nextHopChainingCount, ran-PagingCycle, and ran-NotificationAreaInfo, oneapproach may be for the UE to store these parameters every time the UEreceives a RRCSuspend message, and only delete these parameters when theUE enters RRC_CONNECTED. This may create an ambiguity as to whichparameters the UE should use in the suspend state since the UE could endup with multiple sets of the same parameters.

Certain aspects of the present disclosure and their embodiments mayprovide solutions to these or other challenges. In particular,embodiments described herein introduce a new mechanism to handle a setof inactive parameters (e.g., security context and location-basedparameters used for the integrity token of Resume Request, paging andnotification area parameters) upon receiving a Suspend message inresponse to transmitting an RRC Resume Request. These parameters mayalso be refreshed in the case the UE is performing a Resume Request andreceives Suspend message. In this regard, these parameters may be keptfresh regardless of whether or not the UE enters RRC_CONNECTED. This isdifferent from previous approaches in which the UE is required to enterRRC_CONNECTED and then be re-suspended to refresh these parameters.

Certain embodiments may provide one or more of the following technicaladvantage(s).

Particular embodiments of the present disclosure describe a clear UEbehavior defined for subsequent Resume procedures. In at least some suchembodiments, the UE refreshes the security related parameters whenreceiving a suspend message (or Release messages with a suspendconfiguration or indication).

In at least some such embodiments, this allows the security principle inLTE of using the latest location-based parameters to compute UE'ssecurity integrity token for inclusion in the RRC Resume Request (alsocalled Resume Message Authentication Code for Integrity (MAC-I)) to bemaintained.

Moreover, particular embodiments avoid the need for the network toretain old information created when the UE was last in connected state.That is, it is enough for particular embodiments to maintain the lastcontext from the last time the UE was suspended. This may, for example,reduce network complexity.

FIG. 4 illustrates an example wireless communication network 400,according to one or more embodiments. The wireless communication network400 supports communications between a base station 402 and a UE 404. Thebase station 402, sometimes referred to in applicable standards as anEvolved Node B (eNB) or Fifth Generation (5G) Node B (gNB), providesradio coverage to the UE 404 in a cell 406 of the wireless communicationnetwork 400.

The UE 404 may comprise, for example, a cellular telephone, a smartphone, a laptop computer, a notebook computer, a tablet, aMachine-to-Machine (M2M) communication device (also referred to as aMachine Type Communication (MTC) device), or other device with wirelesscommunication capabilities. The base station 402 transmits data to theUE 404 in the downlink (DL) on the Physical Downlink Shared Channel(PDSCH), the Physical Downlink Control Channel (PDCCH), and the PhysicalBroadcast Channel (PBCH). The UE 404 transmits data to the base station402 in the uplink (UL) on the Physical Uplink Shared Channel (PUSCH).The base station 402 and the UE 404 are configured to operate accordingto the 5G or NR standards.

The cell 406 may be identified by a PCI and/or a cell identity (cellID). The PCI may be obtained by detecting a synchronization signalassociated with the cell 406. The cell ID may be obtained from systeminformation received from the base station 402 and associated with thecell 406.

Similar to LTE, NR will use Orthogonal Frequency Division Multiplexing(OFDM) in the downlink from a network node or base station (also knownas an eNB or gNB) to a UE. In the uplink (i.e., from the UE to gNB),both OFDM and Discrete Fourier Transform (DFT)-spread OFDM will besupported.

The basic NR physical resource for 5G and NR networks can be viewed as atime-frequency grid similar to the one in LTE as illustrated in FIG. 5 ,where each resource element corresponds to one OFDM subcarrier duringone OFDM symbol interval. The spacing of the subcarriers may bekilohertz (kHz), as shown in FIG. 5 and supported in LTE, or may bedifferent, such as those supported in NR.

Furthermore, the resource allocation in LTE is typically described interms of Resource Blocks (RBs), where a RB corresponds to one slot (0.5milliseconds (ms)) in the time domain and 12 contiguous subcarriers inthe frequency domain. An RB is also referred to as Physical RB (PRB).RBs are numbered in the frequency domain, starting with 0 from one endof the system bandwidth. For NR, an RB is also 12 subcarriers infrequency.

With respect to the time domain, embodiments may use the same PRB lengthas LTE, or a different one, depending on the embodiment. According toparticular embodiments, the time domain of downlink and uplinktransmissions in NR is organized into equally-sized subframes (similarto LTE) as shown in FIG. 6 .

Downlink transmissions are dynamically scheduled, i.e., in each subframethe base station transmits Downlink Control Information (DCI) aboutwhich UE 404 data is to be transmitted to and which RBs in the currentdownlink subframe the data is transmitted on. This control signaling istypically transmitted in the first one or two OFDM symbols in eachsubframe in NR. The control information is carried on PDCCH and data iscarried on PDSCH. A UE 404 first detects and decodes PDCCH and if aPDCCH is decoded successfully, it decodes the corresponding PDSCH basedon the decoded control information in the PDCCH. Each UE 404 is assignedwith a unique C-RNTI in the same serving cell. The Cyclic RedundancyCheck (CRC) bits of a PDCCH for a UE 404 is scrambled by the UE 404'sC-RNTI, so a UE 404 recognizes its PDCCH by checking the C-RNTI used toscramble the CRC bits of the PDCCH.

Uplink data transmissions are also dynamically scheduled using PDCCH.Similar to downlink, a UE 404 first decodes uplink grants in PDCCH andthen transmits data over the PUSCH based on the decoded controlinformation in the uplink grant such as modulation order, coding rate,uplink resource allocation, etc.

In LTE, Semi-Persistent Scheduling (SPS) is also supported in bothuplink and downlink, in which a sequence of periodic data transmissionsis activated or deactivated by a single PDCCH. There is no PDCCHtransmitted for data transmissions after activation. In SPS, the PDCCH'sCRC is scrambled by a SPS-C-RNTI, which is configured for a UE 404 ifthe UE 404 supports SPS.

In addition to PUSCH, Physical Uplink Control Channel (PUCCH) is alsosupported in NR to carry Uplink Control Information (UCI) such as HybridAutomatic Repeat Request (HARQ) related Acknowledgement (ACK), NegativeAcknowledgement (NACK), or Channel State Information (CSI) feedback.

The RRC protocol may be used on the Air interface between the UE 404 andthe base station 402 (e.g., transported via the PDCP-Protocol). The RRCprotocol generally relates to certain services and functions of the RRCsublayer, including e.g., connection establishment and releasefunctions, broadcast of system information (e.g., relating to theNon-Access Stratum (NAS) and/or the AS), radio bearer establishment,reconfiguration and release, RRC connection mobility procedures, Qualityof Service (QoS) management functions, UE measurement reporting andreporting control, paging notification and release, and outer loop powercontrol. Moreover, RRC signaling may configure the user and controlplanes according to the network status and allows for Radio ResourceManagement (RRM) strategies to be implemented.

Particular embodiments of RRC are guided by a state machine whichdefines certain specific states in which a UE 404 may be. Particularstates in this state machine have different amounts of radio resourcesassociated with them and these are the resources that the UE 404 may usewhen present and in a given state. Since different amounts of resourcesare available at different states the quality of service that the userexperiences, and the energy consumption of the UE, may be influenced bythis state machine.

Although particular embodiments discussed herein are performed by a UEwhile in the RRC_INACTIVE state in NR, other embodiments may apply inother circumstances. For example, similar embodiments may include:

-   -   LTE procedures instead of NR (e.g., with a UE in the        RRC_INACTIVE state of LTE)    -   Inter-Radio Access Technology (RAT) procedures in RRC_INACTIVE        (e.g., between LTE and NR connected to the same 5G Core Network        (CN)    -   a UE that is in the LTE RRC_CONNECTED state that is suspended to        LTE    -   RRC_INACTIVE, performs mobility and camps on an NR cell (i.e.        becomes in NR RRC_INACTIVE)    -   a UE in NR RRC_CONNECTED that is suspended to NR RRC_INACTIVE,        performs mobility and camps on an LTE cell (i.e. transit to LTE        RRC_INACTIVE).

FIG. 7 depicts a method WW100 in accordance with particular embodiments.As is apparent from the discussion herein, the method WW100 is performedby the UE. The method WW100 includes transmitting an RRC Resume Requestto a base station (block WW105) and receiving an RRC Suspend messagefrom the base station in response to the transmitting (block WW110).While not illustrated, numerous embodiments are described below thatrelate to actions performed by the UE upon receiving the RRC Suspendmessage in response to the transmitted RRC Resume Request. In general,these embodiments relate to replacing or updating at least some of theinformation in the AS context of the UE stored at the UE.

FIG. 8 depicts a method WW200 in accordance with other particularembodiments. As is apparent from the discussion herein, the method WW200is performed by the base station. The method WW200 includes receiving anRRC Resume Request from a wireless device (block WW205), andtransmitting an RRC Suspend message to the wireless device in responseto the receiving (block WW210). While not illustrated, numerousembodiments are described below that relate to actions performed by thebase station upon sending the RRC Suspend message in response to the RRCResume Request. In general, these embodiments relate to replacing orupdating at least some of the information in the AS context of the UEstored at the network side (e.g., at the base station or another networknode).

Note that the apparatuses described above may perform the methods hereinand any other processing by implementing any functional means, modules,units, or circuitry. In one embodiment, for example, the apparatusescomprise respective circuits or circuitry configured to perform thesteps shown in the method figures. The circuits or circuitry in thisregard may comprise circuits dedicated to performing certain functionalprocessing and/or one or more microprocessors in conjunction withmemory. For instance, the circuitry may include one or moremicroprocessor or microcontrollers, as well as other digital hardware,which may include Digital Signal Processors (DSPs), special-purposedigital logic, and the like. The processing circuitry may be configuredto execute program code stored in memory, which may include one orseveral types of memory such as Read Only Memory (ROM), Random AccessMemory, cache memory, flash memory devices, optical storage devices,etc. Program code stored in memory may include program instructions forexecuting one or more telecommunications and/or data communicationsprotocols as well as instructions for carrying out one or more of thetechniques described herein, in several embodiments. In embodiments thatemploy memory, the memory stores program code that, when executed by theone or more processors, carries out the techniques described herein.

FIG. 9 for example illustrates a wireless device YY100 as implemented inaccordance with one or more embodiments. As is apparent from thedescription herein, a UE is one example of the wireless device YY100. Asshown, the wireless device YY100 includes processing circuitry YY110 andcommunication circuitry YY120. The communication circuitry YY120 (e.g.,radio circuitry) is configured to transmit and/or receive information toand/or from one or more other nodes, e.g., via any communicationtechnology. Such communication may occur via one or more antennas thatare either internal or external to the wireless device YY100. Theprocessing circuitry YY110 is configured to perform processing describedabove, such as by executing instructions stored in memory YY190. Theprocessing circuitry YY110 in this regard may implement certainfunctional means, units, or modules. In some embodiments, the processingcircuitry YY110 is configured to execute instructions of a program YY195stored in the memory YY190 of the wireless device YY100.

FIG. 10 illustrates a schematic block diagram of a wireless device YY200in a wireless network according to still other embodiments (for example,the wireless network shown in FIG. 14 ). As is apparent from thedescription herein, a UE is one example of the wireless device YY200. Asshown, the wireless device YY200 implements various functional means,units, or modules, e.g., via the processing circuitry YY110 in FIG. 9and/or via software code. These functional means, units, or modules,e.g., for implementing the method(s) herein, include (for instance) atransmitting unit or module YY210 and a receiving unit or module YY220.The transmitting unit or module YY210 is configured to transmit an RRCResume Request to a base station 402. The receiving unit or module YY220is configured to receive an RRC Suspend message from the base station402 in response to the transmitting.

FIG. 11 illustrates a network node YY300 as implemented in accordancewith one or more embodiments. As is apparent from the descriptionherein, a base station is one example of the network node YY300. Asshown, the network node YY300 includes processing circuitry YY310 andcommunication circuitry YY320. The communication circuitry YY320 isconfigured to transmit and/or receive information to and/or from one ormore other nodes, e.g., via any communication technology. The processingcircuitry YY310 is configured to perform processing described above,such as by executing instructions of a program YY395 stored in memoryYY390. The processing circuitry YY310 in this regard may implementcertain functional means, units, or modules.

FIG. 12 illustrates a schematic block diagram of a network node (e.g.,base station) YY400 in a wireless network according to still otherembodiments (for example, the wireless network shown in FIG. 14 ). As isapparent from the description herein, a base station is one example ofthe network node YY400. As shown, the network node YY400 implementsvarious functional means, units, or modules, e.g., via the processingcircuitry YY310 in FIG. 11 and/or via software code. These functionalmeans, units, or modules, e.g., for implementing the method(s) herein,include (for instance) a receiving unit or module YY410 and atransmitting unit or module YY420. The receiving unit or module YY410 isconfigured to receive an RRC Resume Request from a wireless device 404.The transmitting unit or module YY420 is configured to transmit an RRCSuspend message to the wireless device 404 in response to the receiving.

Those skilled in the art will also appreciate that embodiments hereinfurther include corresponding computer programs.

A computer program comprises instructions which, when executed on atleast one processor of an apparatus, cause the apparatus to carry outany of the respective processing described above. A computer program inthis regard may comprise one or more code modules corresponding to themeans or units described above.

Embodiments further include a carrier containing such a computerprogram. This carrier may comprise one of an electronic signal, opticalsignal, radio signal, or computer readable storage medium.

In this regard, embodiments herein also include a computer programproduct stored on a non-transitory computer readable (storage orrecording) medium and comprising instructions that, when executed by aprocessor of an apparatus, cause the apparatus to perform as describedabove.

Embodiments further include a computer program product comprisingprogram code portions for performing the steps of any of the embodimentsherein when the computer program product is executed by a computingdevice. This computer program product may be stored on a computerreadable recording medium.

Additional embodiments will now be described. At least some of theseembodiments may be described as applicable in certain contexts and/orwireless network types for illustrative purposes, but the embodimentsare similarly applicable in other contexts and/or wireless network typesnot explicitly described.

In a first embodiment, upon receiving an RRC Suspend message (or Releasemessage with some indication for suspend) in response to an RRC ResumeRequest, if the message contains AS security context information the UEoverrides any stored AS security context (if any stored) i.e. it deletesand stores the newly received value.

In a second embodiment, upon receiving an RRC Suspend message (orRelease message with some indication for suspend) in response to an RRCResume Request, if the message contains an Inactive Radio NetworkTemporary Identifier (I-RNTI), the UE overrides any stored I-RNTI (ifany stored), i.e. it deletes and stores the newly received value.

Note (equivalent network embodiments): A counter-part in the networkside shall also perform these updates for security context and I-RNTI(or any kind of resume identifier).

In a third embodiment, upon receiving an RRC Suspend message (or Releasemessage with some indication for suspend) in response to an RRC ResumeRequest, the UE updates location-based parameters, such as the PCI andthe Cell Identity.

In one variant of this third embodiment, this update consists ofdeleting the previously stored PCI and storing the PCI associated to thecell where the UE has sent the Resume Request, i.e. the cell the UE iscamping when it sends the message and receives the Release as aresponse. The PCI is obtained by detecting the Synchronization Signals(SS) associated to that cell, i.e. SS Block(s).

In another variant of this embodiment, this update consists of deletingthe previously stored Cell Identifier and storing the Cell Identifierassociated to the cell where the UE has sent the Resume Request, i.e.the cell the UE is camping when it sends the message and receives theRelease as a response. The Cell Identity can be obtained by readingsystem information associated to that cell.

In another variant of this third embodiment, this update could beindicated whether it shall be done or not by the UE.

Note that there are corresponding network embodiments. That is, acounter-part in the network side shall also perform these updates. Inother words, the AS context is updated such a way that the previouslystored PCI is deleted and the new one is stored. Also, the previouslystored Cell Identity is deleted and the new one is stored.

In a fourth embodiment, upon receiving an RRC Suspend message (orRelease message with some indication for suspend) in response to an RRCResume Request, the UE updates the C-RNTI information.

In one variant of this fourth embodiment, this update consists ofdeleting the previously stored C-RNTI, obtaining the temporary C-RNTIupon performing random access towards a new cell where the UE wants tosend the RRC Resume Request, where the temporary C-RNTI is received inRandom Access Response associated to that cell and storing thattemporary C-RNTI as the new C-RNTI to be used in subsequent ResumeRequest attempts. For example, the C-RNTI can be used as input tocompute the UE's security integrity token to be included in the RRCResume Request.

In another variant of this fourth embodiment, this update consists ofdeleting the previously stored C-RNTI, obtaining the temporary C-RNTIand using it as in the previous variant, except if contention resolutionexists and the C-RNTI is updated. In that case, the updated C-RNTI shallbe stored by the UE to be used in subsequent Resume procedures.

In another variant of this fourth embodiment, this update could beindicated whether it shall be done or not by the UE.

In another variant of this fourth embodiment, this update is done basedon a new C-RNTI received in the Suspend message itself (or the Releasemessage with suspend indication).

In a fifth embodiment, upon receiving an RRC Suspend message (or Releasemessage with some indication for suspend) in response to an RRC ResumeRequest, if the message contains an NCC (nextHopChainingCount), RadioAccess Network (RAN) paging configuration (ran-PagingCycle) or RANNotification Area Configuration (ran-NotificationAreaInfo), the UEoverrides any of these information that is stored (if any stored), i.e.it deletes and stores the newly received value associated. This isdifferent from current draft specification where the UE just stores theparameters.

In a variant of the fifth embodiment, also applicable to the otherembodiments describing an overriding rule, the overriding rule isimplemented using need codes, i.e. a code that indicates to the UE thata parameter is stored and, upon receiving a new one, that previous valueis overridden, i.e. deleted and replaced by the new value. That can beused in combination with procedure text also.

One or more of the solutions described herein may be implemented in,e.g., NR RRC specification 38.331 in accordance with the examples foundin Appendix E, any provisions of which may be applied individually or inany combination.

FIG. 13 illustrates the operation of a UE and a base station inaccordance with at least some aspects of the embodiments of the presentdisclosure described above. As illustrated, the UE transmits an RRCResume Request to the base station (step WT100). In response to the RRCResume Request, the base station transmits, and the UE receives, a RRCSuspend message or an RRC Release message including an indication forsuspend (step WT102). At the UE, in response to receiving the RRCSuspend message or the RRC Release message including the indication forsuspend, the UE replaces information in a stored AS context of the UEwith new information (step WT104). A number of embodiments and variantsthereof are described above with respect to what information in thestored AS context of the UE can be replaced.

More specifically, as discussed above with respect to the “firstembodiment”, upon receiving the RRC Suspend message (or Release messagewith some indication for suspend) in response to an RRC Resume Request,if the message contains AS security context information, the UEoverrides (i.e., replaces) any stored AS security context (if anystored) with the new AS security context information contained in themessage. In other words, the UE determines whether the received RRCSuspend message or RRC release message with some indication of suspendcontains AS security context information. If so, the UE replaces thecorresponding stored AS security context information with the receivedAS security context. In this manner, the stored AS context of the UE isrefreshed (i.e., updated).

In addition or alternatively, as discussed above with respect to the“second embodiment”, upon receiving the RRC Suspend message (or Releasemessage with some indication for suspend) in response to the RRC ResumeRequest, if the message contains an I-RNTI, the UE overrides (i.e.,replaces) any stored I-RNTI (if any stored) with the I-RNTI contained inthe message. In other words, the UE determines whether the received RRCSuspend message or RRC release message with some indication of suspendcontains an I-RNTI. If so, the UE replaces the corresponding storedI-RNTI with the received I-RNTI. In this manner, the stored AS contextof the UE is refreshed (i.e., updated).

In addition or alternatively, as discussed above with respect to the“third embodiment”, upon receiving the RRC Suspend message (or Releasemessage with some indication for suspend) in response to an RRC ResumeRequest, the UE updates location-based parameters, such as the PCI andthe Cell Identity in the stored AS context at the UE. As discussedabove, the PCI and/or Cell Identity are, in some variants, the PCIand/or Cell Identity associated to the cell where the UE has sent theResume Request, i.e. the cell the UE is camping when it sends the RRCResume Request and receives the RRC Suspend message (or RRC Releasemessage with some indication for suspend).

In addition or alternatively, as discussed above with respect to the“fourth embodiment”, upon receiving the RRC Suspend message (or Releasemessage with some indication for suspend) in response to the RRC ResumeRequest, the UE updates the C-RNTI information. In other words, the UEreplaces a stored C-RNTI in the stored AS context of the UE with a newlyobtained C-RNTI, where this newly obtained C-RNTI is associated to thecell in which the UE transmits the RRC Resume Request in step WT100 andreceives the RRC Suspend or RRC Release with some indication of suspendin step WT102.

In addition or alternatively, as discussed above with respect to the“fifth embodiment”, the base station may instruct to the UE as to whichparameters in the stored AS context of the UE are or may be replaced.

In some embodiments, in response to transmitting the RRC Suspend messageor the RRC Release message including the indication for suspend, thebase station may also replace information in a stored AS context of theUE on the network-side, as discussed above (step WT106). The stored AScontext of the UE may be stored by the base station or some othernetwork node. The details of the replacing of the information in thestored AS context are the same as that described above with respect to,e.g., the “first embodiment”, the “second embodiment”, the “thirdembodiment”, and the “fourth embodiment” for the UE. As such, thedetails are not repeated here.

In some embodiments, after replacing the information in the stored AScontext of the UE to provide an updated AS context of the UE, the UEuses the updated AS context of the UE to send a subsequent RRC resumerequest (step WT108). In some embodiments, as discussed above, the UEuses information contained in the updated AS context to calculate asecurity integrity token (e.g., MAC-I) comprised in the subsequent RRCresume request.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 14 .For simplicity, the wireless network of FIG. 14 only depicts networkQQ106, network nodes QQ160 and QQ160 b, and WDs QQ110, QQ110 b, andQQ110 c. In practice, a wireless network may further include anyadditional elements suitable to support communication between wirelessdevices or between a wireless device and another communication device,such as a landline telephone, a service provider, or any other networknode or end device. Of the illustrated components, network node QQ160and wireless device (WD) QQ110 are depicted with additional detail. Thewireless network may provide communication and other types of servicesto one or more wireless devices to facilitate the wireless devices'access to and/or use of the services provided by, or via, the wirelessnetwork.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), LTE, NarrowbandInternet of Things (NB-IoT), and/or other suitable Second, Third,Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards; WirelessLocal Area Network (WLAN) standards, such as the IEEE 802.11 standards;and/or any other appropriate wireless communication standard, such asthe Worldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave, and/or ZigBee standards.

Network QQ106 may comprise one or more backhaul networks, core networks,Internet Protocol (IP) networks, Public Switched Telephone Networks(PSTNs), packet data networks, optical networks, Wide Area Networks(WANs), Local Area Networks (LANs), WLANs, wired networks, wirelessnetworks, metropolitan area networks, and other networks to enablecommunication between devices.

Network node QQ160 and WD QQ110 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, Access Points (APs) (e.g., radio access points), BaseStations (BSs) (e.g., radio base stations, Node Bs, eNBs and gNBs). Basestations may be categorized based on the amount of coverage they provide(or, stated differently, their transmit power level) and may then alsobe referred to as femto base stations, pico base stations, micro basestations, or macro base stations. A base station may be a relay node ora relay donor node controlling a relay. A network node may also includeone or more (or all) parts of a distributed radio base station such ascentralized digital units and/or Remote Radio Units (RRUs), sometimesreferred to as Remote Radio Heads (RRHs). Such remote radio units may ormay not be integrated with an antenna as an antenna integrated radio.Parts of a distributed radio base station may also be referred to asnodes in a Distributed Antenna System (DAS). Yet further examples ofnetwork nodes include Multi-Standard Radio (MSR) equipment such as MSRBSs, network controllers such as Radio Network Controllers (RNCs) orBase Station Controllers (BSCs), Base Transceiver Stations (BTSs),transmission points, transmission nodes, Multi-Cell/MulticastCoordination Entities (MCEs), core network nodes (e.g., Mobile SwitchingCenters (MSCs), Mobility Management Entities (MMEs)), Operation andMaintenance (O&M) nodes, Operations Support System (OSS) nodes,Self-Organizing Network (SON) nodes, positioning nodes (e.g., EvolvedServing Mobile Location Center (E-SMLCs)), and/or Minimization of DriveTests (MDTs). As another example, a network node may be a virtualnetwork node as described in more detail below. More generally, however,network nodes may represent any suitable device (or group of devices)capable, configured, arranged, and/or operable to enable and/or providea wireless device with access to the wireless network or to provide someservice to a wireless device that has accessed the wireless network.

In FIG. 14 , network node QQ160 includes processing circuitry QQ170,device readable medium QQ180, interface QQ190, auxiliary equipmentQQ184, power source QQ186, power circuitry QQ187, and antenna QQ162.Although network node QQ160 illustrated in the example wireless networkof FIG. 14 may represent a device that includes the illustratedcombination of hardware components, other embodiments may comprisenetwork nodes with different combinations of components. It is to beunderstood that a network node comprises any suitable combination ofhardware and/or software needed to perform the tasks, features,functions and methods disclosed herein. Moreover, while the componentsof network node QQ160 are depicted as single boxes located within alarger box, or nested within multiple boxes, in practice, a network nodemay comprise multiple different physical components that make up asingle illustrated component (e.g., device readable medium QQ180 maycomprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may be composed of multiple physicallyseparate components (e.g., a Node B component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node QQ160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple Node Bs.In such a scenario, each unique Node B and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node QQ160 may be configured to support multipleRATs. In such embodiments, some components may be duplicated (e.g.,separate device readable medium QQ180 for the different RATs) and somecomponents may be reused (e.g., the same antenna QQ162 may be shared bythe RATs). Network node QQ160 may also include multiple sets of thevarious illustrated components for different wireless technologiesintegrated into network node QQ160, such as, for example, GSM, WidebandCode Division Multiple Access (WCDMA), LTE, NR, WiFi, or Bluetoothwireless technologies. These wireless technologies may be integratedinto the same or different chip or set of chips and other componentswithin network node QQ160.

Processing circuitry QQ170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry QQ170 may include processinginformation obtained by processing circuitry QQ170 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry QQ170 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, Central Processing Unit(CPU), DSP, Application Specific Integrated Circuit (ASIC), FieldProgrammable Gate Array (FPGA), or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode QQ160 components, such as device readable medium QQ180, networknode QQ160 functionality. For example, processing circuitry QQ170 mayexecute instructions stored in device readable medium QQ180 or in memorywithin processing circuitry QQ170. Such functionality may includeproviding any of the various wireless features, functions, or benefitsdiscussed herein. In some embodiments, processing circuitry QQ170 mayinclude a System on a Chip (SOC).

In some embodiments, processing circuitry QQ170 may include one or moreof Radio Frequency (RF) transceiver circuitry QQ172 and basebandprocessing circuitry QQ174. In some embodiments, RF transceivercircuitry QQ172 and baseband processing circuitry QQ174 may be onseparate chips (or sets of chips), boards, or units, such as radio unitsand digital units. In alternative embodiments, part or all of RFtransceiver circuitry QQ172 and baseband processing circuitry QQ174 maybe on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry QQ170executing instructions stored on device readable medium QQ180 or memorywithin processing circuitry QQ170. In alternative embodiments, some orall of the functionality may be provided by processing circuitry QQ170without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner. In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry QQ170 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry QQ170 alone or toother components of network node QQ160, but are enjoyed by network nodeQQ160 as a whole, and/or by end users and the wireless networkgenerally.

Device readable medium QQ180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, RAM, ROM, mass storage media (forexample, a hard disk), removable storage media (for example, a flashdrive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer-executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry QQ170. Devicereadable medium QQ180 may store any suitable instructions, data orinformation, including a computer program, software, an applicationincluding one or more of logic, rules, code, tables, etc. and/or otherinstructions capable of being executed by processing circuitry QQ170and, utilized by network node QQ160. Device readable medium QQ180 may beused to store any calculations made by processing circuitry QQ170 and/orany data received via interface QQ190. In some embodiments, processingcircuitry QQ170 and device readable medium QQ180 may be considered to beintegrated.

Interface QQ190 is used in the wired or wireless communication ofsignaling and/or data between network node QQ160, network QQ106, and/orWDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s)QQ194 to send and receive data, for example to and from network QQ106over a wired connection. Interface QQ190 also includes radio front endcircuitry QQ192 that may be coupled to, or in certain embodiments a partof, antenna QQ162. Radio front end circuitry QQ192 comprises filtersQQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may beconnected to antenna QQ162 and processing circuitry QQ170. Radio frontend circuitry may be configured to condition signals communicatedbetween antenna QQ162 and processing circuitry QQ170. Radio front endcircuitry QQ192 may receive digital data that is to be sent out to othernetwork nodes or WDs via a wireless connection. Radio front endcircuitry QQ192 may convert the digital data into a radio signal havingthe appropriate channel and bandwidth parameters using a combination offilters QQ198 and/or amplifiers QQ196. The radio signal may then betransmitted via antenna QQ162. Similarly, when receiving data, antennaQQ162 may collect radio signals which are then converted into digitaldata by radio front end circuitry QQ192. The digital data may be passedto processing circuitry QQ170. In other embodiments, the interface maycomprise different components and/or different combinations ofcomponents.

In certain alternative embodiments, network node QQ160 may not includeseparate radio front end circuitry QQ192, instead, processing circuitryQQ170 may comprise radio front end circuitry and may be connected toantenna QQ162 without separate radio front end circuitry QQ192.Similarly, in some embodiments, all or some of RF transceiver circuitryQQ172 may be considered a part of interface QQ190. In still otherembodiments, interface QQ190 may include one or more ports or terminalsQQ194, radio front end circuitry QQ192, and RF transceiver circuitryQQ172, as part of a radio unit (not shown), and interface QQ190 maycommunicate with baseband processing circuitry QQ174, which is part of adigital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna QQ162 may becoupled to radio front end circuitry QQ190 and may be any type ofantenna capable of transmitting and receiving data and/or signalswirelessly. In some embodiments, antenna QQ162 may comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 gigahertz (GHz) and 66 GHz. Anomni-directional antenna may be used to transmit/receive radio signalsin any direction, a sector antenna may be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna maybe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna may be referred to as Multiple Input Multiple Output (MIMO). Incertain embodiments, antenna QQ162 may be separate from network nodeQQ160 and may be connectable to network node QQ160 through an interfaceor port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry QQ187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network nodeQQ160 with power for performing the functionality described herein.Power circuitry QQ187 may receive power from power source QQ186. Powersource QQ186 and/or power circuitry QQ187 may be configured to providepower to the various components of network node QQ160 in a form suitablefor the respective components (e.g., at a voltage and current levelneeded for each respective component). Power source QQ186 may either beincluded in, or external to, power circuitry QQ187 and/or network nodeQQ160. For example, network node QQ160 may be connectable to an externalpower source (e.g., an electricity outlet) via an input circuitry orinterface such as an electrical cable, whereby the external power sourcesupplies power to power circuitry QQ187. As a further example, powersource QQ186 may comprise a source of power in the form of a battery orbattery pack which is connected to, or integrated in, power circuitryQQ187. The battery may provide backup power should the external powersource fail. Other types of power sources, such as photovoltaic devices,may also be used.

Alternative embodiments of network node QQ160 may include additionalcomponents beyond those shown in FIG. 14 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node QQ160 may include user interface equipment to allow inputof information into network node QQ160 and to allow output ofinformation from network node QQ160. This may allow a user to performdiagnostic, maintenance, repair, and other administrative functions fornetwork node QQ160.

As used herein, WD refers to a device capable, configured, arrangedand/or operable to communicate wirelessly with network nodes and/orother wireless devices. Unless otherwise noted, the term WD may be usedinterchangeably herein with UE. Communicating wirelessly may involvetransmitting and/or receiving wireless signals using electromagneticwaves, radio waves, infrared waves, and/or other types of signalssuitable for conveying information through air. In some embodiments, aWD may be configured to transmit and/or receive information withoutdirect human interaction. For instance, a WD may be designed to transmitinformation to a network on a predetermined schedule, when triggered byan internal or external event, or in response to requests from thenetwork. Examples of a WD include, but are not limited to, a smartphone, a mobile phone, a cell phone, a Voice over IP (VoIP) phone, awireless local loop phone, a desktop computer, a Personal DigitalAssistant (PDA), a wireless cameras, a gaming console or device, a musicstorage device, a playback appliance, a wearable terminal device, awireless endpoint, a mobile station, a tablet, a laptop, a LaptopEmbedded Equipment (LEE), a Laptop Mounted Equipment (LME), a smartdevice, a wireless Customer Premise Equipment (CPE), a vehicle-mountedwireless terminal device, etc. A WD may support Device-to-Device (D2D)communication, for example by implementing a 3GPP standard for sidelinkcommunication, Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure(V2I), Vehicle-to-Everything (V2X) and may in this case be referred toas a D2D communication device. As yet another specific example, in anInternet of Things (IoT) scenario, a WD may represent a machine or otherdevice that performs monitoring and/or measurements, and transmits theresults of such monitoring and/or measurements to another WD and/or anetwork node. The WD may in this case be a M2M device, which may in a3GPP context be referred to as an MTC device. As one particular example,the WD may be a UE implementing the 3GPP NB-IoT standard. Particularexamples of such machines or devices are sensors, metering devices suchas power meters, industrial machinery, or home or personal appliances(e.g. refrigerators, televisions, etc.) personal wearables (e.g.,watches, fitness trackers, etc.). In other scenarios, a WD may representa vehicle or other equipment that is capable of monitoring and/orreporting on its operational status or other functions associated withits operation. A WD as described above may represent the endpoint of awireless connection, in which case the device may be referred to as awireless terminal. Furthermore, a WD as described above may be mobile,in which case it may also be referred to as a mobile device or a mobileterminal.

As illustrated, wireless device QQ110 includes antenna QQ111, interfaceQQ114, processing circuitry QQ120, device readable medium QQ130, userinterface equipment QQ132, auxiliary equipment QQ134, power source QQ136and power circuitry QQ137. WD QQ110 may include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, NB-IoT, or Bluetooth wireless technologies, just to mention afew. These wireless technologies may be integrated into the same ordifferent chips or set of chips as other components within WD QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface QQ114. In certain alternative embodiments, antenna QQ111 maybe separate from WD QQ110 and be connectable to WD QQ110 through aninterface or port. Antenna QQ111, interface QQ114, and/or processingcircuitry QQ120 may be configured to perform any receiving ortransmitting operations described herein as being performed by a WD. Anyinformation, data and/or signals may be received from a network nodeand/or another WD. In some embodiments, radio front end circuitry and/orantenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitryQQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one ormore filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114is connected to antenna QQ111 and processing circuitry QQ120, and isconfigured to condition signals communicated between antenna QQ111 andprocessing circuitry QQ120. Radio front end circuitry QQ112 may becoupled to or a part of antenna QQ111. In some embodiments, WD QQ110 maynot include separate radio front end circuitry QQ112; rather, processingcircuitry QQ120 may comprise radio front end circuitry and may beconnected to antenna QQ111. Similarly, in some embodiments, some or allof RF transceiver circuitry QQ122 may be considered a part of interfaceQQ114. Radio front end circuitry QQ112 may receive digital data that isto be sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry QQ112 may convert the digital data into aradio signal having the appropriate channel and bandwidth parametersusing a combination of filters QQ118 and/or amplifiers QQ116. The radiosignal may then be transmitted via antenna QQ111. Similarly, whenreceiving data, antenna QQ111 may collect radio signals which are thenconverted into digital data by radio front end circuitry QQ112. Thedigital data may be passed to processing circuitry QQ120. In otherembodiments, the interface may comprise different components and/ordifferent combinations of components.

Processing circuitry QQ120 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, orany other suitable computing device, resource, or combination ofhardware, software, and/or encoded logic operable to provide, eitheralone or in conjunction with other WD QQ110 components, such as devicereadable medium QQ130, WD QQ110 functionality. Such functionality mayinclude providing any of the various wireless features or benefitsdiscussed herein. For example, processing circuitry QQ120 may executeinstructions stored in device readable medium QQ130 or in memory withinprocessing circuitry QQ120 to provide the functionality disclosedherein.

As illustrated, processing circuitry QQ120 includes one or more of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitryQQ120 of WD QQ110 may comprise a SOC. In some embodiments, RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be on separate chips or setsof chips. In alternative embodiments, part or all of baseband processingcircuitry QQ124 and application processing circuitry QQ126 may becombined into one chip or set of chips, and RF transceiver circuitryQQ122 may be on a separate chip or set of chips. In still alternativeembodiments, part or all of RF transceiver circuitry QQ122 and basebandprocessing circuitry QQ124 may be on the same chip or set of chips, andapplication processing circuitry QQ126 may be on a separate chip or setof chips. In yet other alternative embodiments, part or all of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be combined in the same chipor set of chips. In some embodiments, RF transceiver circuitry QQ122 maybe a part of interface QQ114. RF transceiver circuitry QQ122 maycondition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry QQ120 executing instructions stored on device readable mediumQQ130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry QQ120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry QQ120 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry QQ120 alone or to other componentsof WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end usersand the wireless network generally.

Processing circuitry QQ120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry QQ120, may include processinginformation obtained by processing circuitry QQ120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD QQ110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium QQ130 may be operable to store a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry QQ120. Device readable medium QQ130 may includecomputer memory (e.g., RAM or ROM), mass storage media (e.g., a harddisk), removable storage media (e.g., a CD or a DVD), and/or any othervolatile or non-volatile, non-transitory device readable and/or computerexecutable memory devices that store information, data, and/orinstructions that may be used by processing circuitry QQ120. In someembodiments, processing circuitry QQ120 and device readable medium QQ130may be considered to be integrated.

User interface equipment QQ132 may provide components that allow for ahuman user to interact with WD QQ110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipmentQQ132 may be operable to produce output to the user and to allow theuser to provide input to WD QQ110. The type of interaction may varydepending on the type of user interface equipment QQ132 installed in WDQQ110. For example, if WD QQ110 is a smart phone, the interaction may bevia a touch screen; if WD QQ110 is a smart meter, the interaction may bethrough a screen that provides usage (e.g., the number of gallons used)or a speaker that provides an audible alert (e.g., if smoke isdetected). User interface equipment QQ132 may include input interfaces,devices and circuits, and output interfaces, devices and circuits. Userinterface equipment QQ132 is configured to allow input of informationinto WD QQ110, and is connected to processing circuitry QQ120 to allowprocessing circuitry QQ120 to process the input information. Userinterface equipment QQ132 may include, for example, a microphone, aproximity or other sensor, keys/buttons, a touch display, one or morecameras, a Universal Serial Bus (USB) port, or other input circuitry.User interface equipment QQ132 is also configured to allow output ofinformation from WD QQ110, and to allow processing circuitry QQ120 tooutput information from WD QQ110. User interface equipment QQ132 mayinclude, for example, a speaker, a display, vibrating circuitry, a USBport, a headphone interface, or other output circuitry. Using one ormore input and output interfaces, devices, and circuits, of userinterface equipment QQ132, WD QQ110 may communicate with end usersand/or the wireless network, and allow them to benefit from thefunctionality described herein.

Auxiliary equipment QQ134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD QQ110 may further comprise power circuitryQQ137 for delivering power from power source QQ136 to the various partsof WD QQ110 which need power from power source QQ136 to carry out anyfunctionality described or indicated herein. Power circuitry QQ137 mayin certain embodiments comprise power management circuitry. Powercircuitry QQ137 may additionally or alternatively be operable to receivepower from an external power source; in which case WD QQ110 may beconnectable to the external power source (such as an electricity outlet)via input circuitry or an interface such as an electrical power cable.Power circuitry QQ137 may also in certain embodiments be operable todeliver power from an external power source to power source QQ136. Thismay be, for example, for the charging of power source QQ136. Powercircuitry QQ137 may perform any formatting, converting, or othermodification to the power from power source QQ136 to make the powersuitable for the respective components of WD QQ110 to which power issupplied.

FIG. 15 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE may represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE mayrepresent a device that is not intended for sale to, or operation by, anend user but which may be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE QQ2200 may be any UE identifiedby the Third Generation Partnership Project (3GPP), including a NB-IoTUE, a MTC UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustratedin Figure is one example of a WD configured for communication inaccordance with one or more communication standards promulgated by the3GPP, such as 3GPP's GSM, UMTS, LTE, and/or standards. As mentionedpreviously, the terms WD and UE may be used interchangeable.Accordingly, although FIG. 15 is a UE, the components discussed hereinare equally applicable to a WD, and vice-versa.

In FIG. 15 , UE QQ200 includes processing circuitry QQ201 that isoperatively coupled to input/output interface QQ205, RF interface QQ209,network connection interface QQ211, memory QQ215 including RAM QQ217,ROM QQ219, and storage medium QQ221 or the like, communication subsystemQQ231, power source QQ233, and/or any other component, or anycombination thereof. Storage medium QQ221 includes operating systemQQ223, application program QQ225, and data QQ227. In other embodiments,storage medium QQ221 may include other similar types of information.Certain UEs may utilize all of the components shown in Figure or only asubset of the components. The level of integration between thecomponents may vary from one UE to another UE. Further, certain UEs maycontain multiple instances of a component, such as multiple processors,memories, transceivers, transmitters, receivers, etc.

In FIG. 15 , processing circuitry QQ201 may be configured to processcomputer instructions and data. Processing circuitry QQ201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or DSP, togetherwith appropriate software; or any combination of the above. For example,the processing circuitry QQ201 may include two CPUs. Data may beinformation in a form suitable for use by a computer.

In the depicted embodiment, input/output interface QQ205 may beconfigured to provide a communication interface to an input device,output device, or input and output device. UE QQ200 may be configured touse an output device via input/output interface QQ205. An output devicemay use the same type of interface port as an input device. For example,a USB port may be used to provide input to and output from UE QQ200. Theoutput device may be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE QQ200 may be configured to use aninput device via input/output interface QQ205 to allow a user to captureinformation into UE QQ200. The input device may include atouch-sensitive or presence-sensitive display, a camera (e.g., a digitalcamera, a digital video camera, a web camera, etc.), a microphone, asensor, a mouse, a trackball, a directional pad, a trackpad, a scrollwheel, a smartcard, and the like. The presence-sensitive display mayinclude a capacitive or resistive touch sensor to sense input from auser. A sensor may be, for instance, an accelerometer, a gyroscope, atilt sensor, a force sensor, a magnetometer, an optical sensor, aproximity sensor, another like sensor, or any combination thereof. Forexample, the input device may include an accelerometer, a magnetometer,a digital camera, a microphone, and/or an optical sensor.

In FIG. 15 , RF interface QQ209 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface QQ211 may beconfigured to provide a communication interface to network QQ243 a.Network QQ243 a may encompass wired and/or wireless networks such as aLAN, a WAN, a computer network, a wireless network, a telecommunicationsnetwork, another like network or any combination thereof. For example,network QQ243 a may comprise a WiFi network. Network connectioninterface QQ211 may be configured to include a receiver and atransmitter interface used to communicate with one or more other devicesover a communication network according to one or more communicationprotocols, such as Ethernet, Transmission Control Protocol (TCP)/IP,Synchronous Optical Networking (SONET), Asynchronous Transfer Mode(ATM), or the like. Network connection interface QQ211 may implementreceiver and transmitter functionality appropriate to the communicationnetwork links (e.g., optical, electrical, and the like). The transmitterand receiver functions may share circuit components, software orfirmware, or alternatively may be implemented separately.

RAM QQ217 may be configured to interface via bus QQ202 to processingcircuitry QQ201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM QQ219may be configured to provide computer instructions or data to processingcircuitry QQ201. For example, ROM QQ219 may be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage mediumQQ221 may be configured to include memory such as RAM, ROM, ProgrammableROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium QQ221 may be configured toinclude operating system QQ223, application program QQ225 such as a webbrowser application, a widget or gadget engine or another application,and data file QQ227. Storage medium QQ221 may store, for use by UEQQ200, any of a variety of various operating systems or combinations ofoperating systems.

Storage medium QQ221 may be configured to include a number of physicaldrive units, such as Redundant Array of Independent Disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, High Density Digital Versatile Disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, Holographic Digital Data Storage (HDDS) optical disc drive,external mini-Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM(SDRAM), external micro-DIMM SDRAM, smartcard memory such as aSubscriber Identity Module (SIM) or a Removable User Identity Module(RUIM), other memory, or any combination thereof. Storage medium QQ221may allow UE QQ200 to access computer-executable instructions,application programs or the like, stored on transitory or non-transitorymemory media, to off-load data, or to upload data. An article ofmanufacture, such as one utilizing a communication system may betangibly embodied in storage medium QQ221, which may comprise a devicereadable medium.

In FIG. 15 , processing circuitry QQ201 may be configured to communicatewith network QQ243 b using communication subsystem QQ231. Network QQ243a and network QQ243 b may be the same network or networks or differentnetwork or networks. Communication subsystem QQ231 may be configured toinclude one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a RAN according to one ormore communication protocols, such as IEEE 802.11, Code DivisionMultiple Access (CDMA), WCDMA, GSM, LTE, Universal Terrestrial RadioAccess Network (UTRAN), WiMax, or the like. Each transceiver may includetransmitter QQ233 and/or receiver QQ235 to implement transmitter orreceiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter QQ233and receiver QQ235 of each transceiver may share circuit components,software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem QQ231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the Global Positioning System (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem QQ231 may include cellularcommunication, WiFi communication, Bluetooth communication, and GPScommunication. Network QQ243 b may encompass wired and/or wirelessnetworks such as a LAN, a WAN, a computer network, a wireless network, atelecommunications network, another like network or any combinationthereof. For example, network QQ243 b may be a cellular network, a WiFinetwork, and/or a near-field network. Power source QQ213 may beconfigured to provide Alternating Current (AC) or Direct Current (DC)power to components of UE QQ200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE QQ200 or partitioned acrossmultiple components of UE QQ200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystemQQ231 may be configured to include any of the components describedherein. Further, processing circuitry QQ201 may be configured tocommunicate with any of such components over bus QQ202. In anotherexample, any of such components may be represented by programinstructions stored in memory that when executed by processing circuitryQQ201 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components may be partitionedbetween processing circuitry QQ201 and communication subsystem QQ231. Inanother example, the non-computationally intensive functions of any ofsuch components may be implemented in software or firmware and thecomputationally intensive functions may be implemented in hardware.

FIG. 16 is a schematic block diagram illustrating a virtualizationenvironment QQ300 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments QQ300 hosted byone or more of hardware nodes QQ330. Further, in embodiments in whichthe virtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications QQ320(which may alternatively be called software instances, virtualappliances, network functions, virtual nodes, virtual network functions,etc.) operative to implement some of the features, functions, and/orbenefits of some of the embodiments disclosed herein. Applications QQ320are run in virtualization environment QQ300 which provides hardwareQQ330 comprising processing circuitry QQ360 and memory QQ390. MemoryQQ390 contains instructions QQ395 executable by processing circuitryQQ360 whereby application QQ320 is operative to provide one or more ofthe features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose orspecial-purpose network hardware devices QQ330 comprising a set of oneor more processors or processing circuitry QQ360, which may becommercial off-the-shelf (COTS) processors, dedicated ASICs, or anyother type of processing circuitry including digital or analog hardwarecomponents or special purpose processors. Each hardware device maycomprise memory QQ390-1 which may be non-persistent memory fortemporarily storing instructions QQ395 or software executed byprocessing circuitry QQ360. Each hardware device may comprise one ormore Network Interface Controllers (NICs) QQ370, also known as networkinterface cards, which include physical network interface QQ380. Eachhardware device may also include non-transitory, persistent,machine-readable storage media QQ390-2 having stored therein softwareQQ395 and/or instructions executable by processing circuitry QQ360.Software QQ395 may include any type of software including software forinstantiating one or more virtualization layers QQ350 (also referred toas hypervisors), software to execute virtual machines QQ340 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer QQ350 or hypervisor. Differentembodiments of the instance of virtual appliance QQ320 may beimplemented on one or more of virtual machines QQ340, and theimplementations may be made in different ways.

During operation, processing circuitry QQ360 executes software QQ395 toinstantiate the hypervisor or virtualization layer QQ350, which maysometimes be referred to as a Virtual Machine Monitor (VMM).Virtualization layer QQ350 may present a virtual operating platform thatappears like networking hardware to virtual machine QQ340.

As shown in FIG. 16 , hardware QQ330 may be a standalone network nodewith generic or specific components. Hardware QQ330 may comprise antennaQQ3225 and may implement some functions via virtualization.Alternatively, hardware QQ330 may be part of a larger cluster ofhardware (e.g. such as in a data center or CPE) where many hardwarenodes work together and are managed via Management and Orchestration(MANO) QQ3100, which, among others, oversees lifecycle management ofapplications QQ320.

Virtualization of the hardware is in some contexts referred to asNetwork Function Virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and CPE.

In the context of NFV, virtual machine QQ340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines QQ340, and that part of hardware QQ330 that executes thatvirtual machine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines QQ340, forms a separate Virtual Network Elements (VNEs).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines QQ340 on top of hardware networking infrastructureQQ330 and corresponds to application QQ320 in FIG. 16 .

In some embodiments, one or more radio units QQ3200 that each includeone or more transmitters QQ3220 and one or more receivers QQ3210 may becoupled to one or more antennas QQ3225. Radio units QQ3200 maycommunicate directly with hardware nodes QQ330 via one or moreappropriate network interfaces and may be used in combination with thevirtual components to provide a virtual node with radio capabilities,such as a radio access node or a base station.

In some embodiments, some signaling can be effected with the use ofcontrol system QQ3230 which may alternatively be used for communicationbetween the hardware nodes QQ330 and radio units QQ3200.

FIG. 17 illustrates a telecommunication network connected via anintermediate network to a host computer in accordance with someembodiments. In particular, with reference to FIG. 17 , in accordancewith an embodiment, a communication system includes telecommunicationnetwork QQ410, such as a 3GPP-type cellular network, which comprisesaccess network QQ411, such as a RAN, and core network QQ414. Accessnetwork QQ411 comprises a plurality of base stations QQ412 a, QQ412 b,QQ412 c, such as Node Bs, eNBs, gNBs or other types of wireless accesspoints, each defining a corresponding coverage area QQ413 a, QQ413 b,QQ413 c. Each base station QQ412 a, QQ412 b, QQ412 c is connectable tocore network QQ414 over a wired or wireless connection QQ415. A first UEQQ491 located in coverage area QQ413 c is configured to wirelesslyconnect to, or be paged by, the corresponding base station QQ412 c. Asecond UE QQ492 in coverage area QQ413 a is wirelessly connectable tothe corresponding base station QQ412 a. While a plurality of UEs QQ491,QQ492 are illustrated in this example, the disclosed embodiments areequally applicable to a situation where a sole UE is in the coveragearea or where a sole UE is connecting to the corresponding base stationQQ412.

Telecommunication network QQ410 is itself connected to host computerQQ430, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server, oras processing resources in a server farm. Host computer QQ430 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections QQ421 and QQ422 between telecommunication network QQ410 andhost computer QQ430 may extend directly from core network QQ414 to hostcomputer QQ430 or may go via an optional intermediate network QQ420.Intermediate network QQ420 may be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network QQ420,if any, may be a backbone network or the Internet; in particular,intermediate network QQ420 may comprise two or more sub-networks (notshown).

The communication system of FIG. 17 as a whole enables connectivitybetween the connected UEs QQ491, QQ492 and host computer QQ430. Theconnectivity may be described as an Over-the-Top (OTT) connection QQ450.Host computer QQ430 and the connected UEs QQ491, QQ492 are configured tocommunicate data and/or signaling via OTT connection QQ450, using accessnetwork QQ411, core network QQ414, any intermediate network QQ420 andpossible further infrastructure (not shown) as intermediaries. OTTconnection QQ450 may be transparent in the sense that the participatingcommunication devices through which OTT connection QQ450 passes areunaware of routing of uplink and downlink communications. For example,base station QQ412 may not or need not be informed about the pastrouting of an incoming downlink communication with data originating fromhost computer QQ430 to be forwarded (e.g., handed over) to a connectedUE QQ491. Similarly, base station QQ412 need not be aware of the futurerouting of an outgoing uplink communication originating from the UEQQ491 towards the host computer QQ430.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 18 . FIG. 18 illustrateshost computer communicating via a base station with a user equipmentover a partially wireless connection in accordance with someembodiments. In communication system QQ500, host computer QQ510comprises hardware QQ515 including communication interface QQ516configured to set up and maintain a wired or wireless connection with aninterface of a different communication device of communication systemQQ500. Host computer QQ510 further comprises processing circuitry QQ518,which may have storage and/or processing capabilities. In particular,processing circuitry QQ518 may comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Host computer QQ510 further comprises software QQ511,which is stored in or accessible by host computer QQ510 and executableby processing circuitry QQ518. Software QQ511 includes host applicationQQ512. Host application QQ512 may be operable to provide a service to aremote user, such as UE QQ530 connecting via OTT connection QQ550terminating at UE QQ530 and host computer QQ510. In providing theservice to the remote user, host application QQ512 may provide user datawhich is transmitted using OTT connection QQ550.

Communication system QQ500 further includes base station QQ520 providedin a telecommunication system and comprising hardware QQ525 enabling itto communicate with host computer QQ510 and with UE QQ530. HardwareQQ525 may include communication interface QQ526 for setting up andmaintaining a wired or wireless connection with an interface of adifferent communication device of communication system QQ500, as well asradio interface QQ527 for setting up and maintaining at least wirelessconnection QQ570 with UE QQ530 located in a coverage area (not shown inFIG. 18 ) served by base station QQ520. Communication interface QQ526may be configured to facilitate connection QQ560 to host computer QQ510.Connection QQ560 may be direct or it may pass through a core network(not shown in FIG. 18 ) of the telecommunication system and/or throughone or more intermediate networks outside the telecommunication system.In the embodiment shown, hardware QQ525 of base station QQ520 furtherincludes processing circuitry QQ528, which may comprise one or moreprogrammable processors, ASICs, FPGAs, or combinations of these (notshown) adapted to execute instructions. Base station QQ520 further hassoftware QQ521 stored internally or accessible via an externalconnection.

Communication system QQ500 further includes UE QQ530 already referredto. Its hardware QQ535 may include radio interface QQ537 configured toset up and maintain wireless connection QQ570 with a base stationserving a coverage area in which UE QQ530 is currently located. HardwareQQ535 of UE QQ530 further includes processing circuitry QQ538, which maycomprise one or more programmable processors, ASICs, FPGAs, orcombinations of these (not shown) adapted to execute instructions. UEQQ530 further comprises software QQ531, which is stored in or accessibleby UE QQ530 and executable by processing circuitry QQ538. Software QQ531includes client application QQ532. Client application QQ532 may beoperable to provide a service to a human or non-human user via UE QQ530,with the support of host computer QQ510. In host computer QQ510, anexecuting host application QQ512 may communicate with the executingclient application QQ532 via OTT connection QQ550 terminating at UEQQ530 and host computer QQ510. In providing the service to the user,client application QQ532 may receive request data from host applicationQQ512 and provide user data in response to the request data. OTTconnection QQ550 may transfer both the request data and the user data.Client application QQ532 may interact with the user to generate the userdata that it provides.

It is noted that host computer QQ510, base station QQ520 and UE QQ530illustrated in FIG. 18 may be similar or identical to host computerQQ430, one of base stations QQ412 a, QQ412 b, QQ412 c and one of UEsQQ491, QQ492 of FIG. 17 , respectively. This is to say, the innerworkings of these entities may be as shown in FIG. 18 and independently,the surrounding network topology may be that of FIG. 17 .

In FIG. 18 , OTT connection QQ550 has been drawn abstractly toillustrate the communication between host computer QQ510 and UE QQ530via base station QQ520, without explicit reference to any intermediarydevices and the precise routing of messages via these devices. Networkinfrastructure may determine the routing, which it may be configured tohide from UE QQ530 or from the service provider operating host computerQQ510, or both. While OTT connection QQ550 is active, the networkinfrastructure may further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection QQ570 between UE QQ530 and base station QQ520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE QQ530 using OTT connectionQQ550, in which wireless connection QQ570 forms the last segment. Moreprecisely, the teachings of these embodiments may improve securityand/or reduce network complexity over alternatives.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection QQ550 between hostcomputer QQ510 and UE QQ530, in response to variations in themeasurement results. The measurement procedure and/or the networkfunctionality for reconfiguring OTT connection QQ550 may be implementedin software QQ511 and hardware QQ515 of host computer QQ510 or insoftware QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments,sensors (not shown) may be deployed in or in association withcommunication devices through which OTT connection QQ550 passes; thesensors may participate in the measurement procedure by supplying valuesof the monitored quantities exemplified above, or supplying values ofother physical quantities from which software QQ511, QQ531 may computeor estimate the monitored quantities. The reconfiguring of OTTconnection QQ550 may include message format, retransmission settings,preferred routing etc.; the reconfiguring need not affect base stationQQ520, and it may be unknown or imperceptible to base station QQ520.Such procedures and functionalities may be known and practiced in theart. In certain embodiments, measurements may involve proprietary UEsignaling facilitating host computer QQ510's measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that software QQ511 and QQ531 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection QQ550 while it monitors propagation times, errors etc.

FIG. 19 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 17 and 18 . Forsimplicity of the present disclosure, only drawing references to FIG. 19will be included in this section. In step QQ610, the host computerprovides user data. In substep QQ611 (which may be optional) of stepQQ610, the host computer provides the user data by executing a hostapplication. In step QQ620, the host computer initiates a transmissioncarrying the user data to the UE. In step QQ630 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step QQ640 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 20 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 17 and 18 . Forsimplicity of the present disclosure, only drawing references to FIG. 20will be included in this section. In step QQ710 of the method, the hostcomputer provides user data. In an optional substep (not shown) the hostcomputer provides the user data by executing a host application. In stepQQ720, the host computer initiates a transmission carrying the user datato the UE. The transmission may pass via the base station, in accordancewith the teachings of the embodiments described throughout thisdisclosure. In step QQ730 (which may be optional), the UE receives theuser data carried in the transmission.

FIG. 21 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 17 and 18 . Forsimplicity of the present disclosure, only drawing references to FIG. 21will be included in this section. In step QQ810 (which may be optional),the UE receives input data provided by the host computer. Additionallyor alternatively, in step QQ820, the UE provides user data. In substepQQ821 (which may be optional) of step QQ820, the UE provides the userdata by executing a client application. In substep QQ811 (which may beoptional) of step QQ810, the UE executes a client application whichprovides the user data in reaction to the received input data providedby the host computer. In providing the user data, the executed clientapplication may further consider user input received from the user.Regardless of the specific manner in which the user data was provided,the UE initiates, in substep QQ830 (which may be optional), transmissionof the user data to the host computer. In step QQ840 of the method, thehost computer receives the user data transmitted from the UE, inaccordance with the teachings of the embodiments described throughoutthis disclosure.

FIG. 22 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 17 and 18 . Forsimplicity of the present disclosure, only drawing references to FIG. 22will be included in this section. In step QQ910 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep QQ920 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In stepQQ930 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include DSPs, special-purpose digital logic, and thelike. The processing circuitry may be configured to execute program codestored in memory, which may include one or several types of memory suchas ROM, RAM, cache memory, flash memory devices, optical storagedevices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thedescription.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

Some of the embodiments contemplated herein are described more fullywith reference to the accompanying drawings. Other embodiments, however,are contained within the scope of the subject matter disclosed herein.The disclosed subject matter should not be construed as limited to onlythe embodiments set forth herein; rather, these embodiments are providedby way of example to convey the scope of the subject matter to thoseskilled in the art. Additional information may also be found in thedocument(s) provided in the Appendices.

Some example embodiments disclosed herein include:

Group A Embodiments

Embodiment 1: A method of Radio Resource Control (RRC) signaling,performed by a wireless device, the method comprising:

-   -   transmitting an RRC Resume Request to a base station; and    -   receiving an RRC Suspend message from the base station in        response to the transmitting.

Embodiment 2: The method of embodiment 1, further comprising storing oneor more parameters comprised in the RRC Suspend message, the parameterscomprising one or more of:

-   -   Access Stratum (AS) security context information;    -   an Inactive Radio Network Temporary Identifier (I-RNTI);    -   a nextHopChainingCount (NCC);    -   a Radio Access Network (RAN) paging configuration        (ran-PagingCycle); or a RAN Notification Area Configuration        (ran-NotificationAreaInfo).

Embodiment 3: The method of embodiment 2, wherein storing the parameterscomprises replacing previously-stored AS security context informationwith the AS security context information in the RRC Suspend message.

Embodiment 4: The method of any of embodiments 2-3, wherein storing theone or more parameters comprises replacing a previously-stored NCC withthe NCC in the RRC Suspend message.

Embodiment 5: The method of any of embodiments 2-4, wherein storing theone or more parameters comprises replacing a previously-storedran-PagingCycle with the ran-PagingCycle in the RRC Suspend message.

Embodiment 6: The method of any of embodiments 2-5, wherein storing theone or more parameters comprises replacing a previously-storedran-NotificationAreaInfo with the ran-NotificationAreaInfo in the RRCSuspend message.

Embodiment 7: The method of any of embodiments 2-6, further comprisingreceiving an instruction from the base station to store the one or moreparameters comprised in the RRC Suspend message.

Embodiment 8: The method of any of the preceding embodiments, furthercomprising updating one or more location-based parameters responsive toreceiving the RRC Suspend message.

Embodiment 9: The method of embodiment 8, wherein the location-basedparameters comprise a Physical Cell Identity (PCI), a Cell Identity(Cell ID), and/or a Cell Radio Network Temporary Identifier (C-RNTI).

Embodiment 10: The method of embodiment 9, further comprising obtainingthe PCI by detecting a synchronization signal associated with a cellserved by the base station.

Embodiment 11: The method of any of embodiments 9-10, further comprisingobtaining the cell ID from system information received from the basestation and associated with a cell served by the base station.

Embodiment 12: The method of any of embodiments 9-11, further comprisingperforming random access to a cell served by the base station to obtainthe C-RNTI.

Embodiment 13: The method of embodiment 12, wherein transmitting the RRCResume Request is in response to obtaining the C-RNTI.

Embodiment 14: The method of any of embodiments 8-13, further comprisingreceiving an instruction from the base station to perform the updating.

Embodiment 15: The method of any of the preceding embodiments, whereinreceiving the RRC Suspend message comprises receiving an RRC Releasemessage comprising an indication to suspend.

Embodiment AA: The method of any of the previous embodiments, furthercomprising:

-   -   providing user data; and    -   forwarding the user data to a host computer via the transmission        to the base station.

Group B Embodiments

Embodiment 16: A method of Radio Resource Control (RRC) signaling,performed by a base station, the method comprising:

-   -   receiving an RRC Resume Request from a wireless device; and    -   transmitting an RRC Suspend message to the wireless device in        response to the receiving.

Embodiment 17: The method of embodiment 16, wherein transmitting the RRCSuspend message comprises transmitting an RRC Release message comprisingan indication to suspend.

Embodiment 18: The method of any of embodiments 16-17, wherein the RRCSuspend message comprises one or more parameters, the parameterscomprising one or more of:

-   -   Access Stratum (AS) security context information;    -   an Inactive Radio Network Temporary Identifier (I-RNTI);    -   a nextHopChainingCount (NCC);    -   a Radio Access Network (RAN) paging configuration        (ran-PagingCycle); or    -   a RAN Notification Area Configuration        (ran-NotificationAreaInfo).

Embodiment 19: The method of any of embodiments 17-18, furthercomprising transmitting, to the wireless device, an instruction to storethe one or more parameters comprised in the RRC Suspend message.

Embodiment 20: The method of any of embodiments 16-19, furthercomprising transmitting, to the wireless device and in response toreceiving the RRC Resume Request, an instruction to update one or morelocation-based parameters.

Embodiment 21: The method of embodiment 20, wherein the location-basedparameters comprise a Physical Cell Identity (PCI), a Cell Identity(Cell ID), and/or a Cell Radio Network Temporary Identifier (C-RNTI).

Embodiment 22: The method of embodiment 21, further comprisingtransmitting a synchronization signal comprising the PCI and associatedwith a cell served by the base station.

Embodiment 23: The method of any of embodiments 21-22, furthercomprising transmitting system information associated with a cell servedby the base station and comprising the cell ID.

Embodiment BB: The method of any of the previous embodiments, furthercomprising:

-   -   obtaining user data; and    -   forwarding the user data to a host computer or a wireless        device.

Group C Embodiments

Embodiment C1: A wireless device configured to perform any of the stepsof any of the Group A embodiments.

Embodiment C2: A wireless device comprising:

-   -   processing circuitry configured to perform any of the steps of        any of the Group A embodiments; and    -   power supply circuitry configured to supply power to the        wireless device.

Embodiment C3: A wireless device comprising processing circuitry andmemory, the memory containing instructions executable by the processingcircuitry whereby the wireless device is configured to perform any ofthe steps of any of the Group A embodiments.

Embodiment C4: A user equipment (UE) comprising:

-   -   an antenna configured to send and receive wireless signals;    -   radio front-end circuitry connected to the antenna and to        processing circuitry, and configured to condition signals        communicated between the antenna and the processing circuitry;    -   the processing circuitry being configured to perform any of the        steps of any of the Group A embodiments;    -   an input interface connected to the processing circuitry and        configured to allow input of information into the UE to be        processed by the processing circuitry;    -   an output interface connected to the processing circuitry and        configured to output information from the UE that has been        processed by the processing circuitry; and    -   a battery connected to the processing circuitry and configured        to supply power to the UE.

Embodiment C5: A computer program comprising instructions which, whenexecuted by at least one processor of a wireless device, causes thewireless device to carry out the steps of any of the Group Aembodiments.

Embodiment C6: A carrier containing the computer program of embodimentC5, wherein the carrier is one of an electronic signal, optical signal,radio signal, or computer readable storage medium.

Embodiment C7: A base station configured to perform any of the steps ofany of the Group B embodiments.

Embodiment C8: A base station comprising:

-   -   processing circuitry configured to perform any of the steps of        any of the Group B embodiments;    -   power supply circuitry configured to supply power to the base        station.

Embodiment C9: A base station comprising processing circuitry andmemory, the memory containing instructions executable by the processingcircuitry whereby the base station is configured to perform any of thesteps of any of the Group B embodiments.

Embodiment C10: A computer program comprising instructions which, whenexecuted by at least one processor of a base station, causes the basestation to carry out the steps of any of the Group B embodiments.

Embodiment C11: A carrier containing the computer program of embodimentC10, wherein the carrier is one of an electronic signal, optical signal,radio signal, or computer readable storage medium.

Group D Embodiments

Embodiment D1: A communication system including a host computercomprising:

-   -   processing circuitry configured to provide user data; and    -   a communication interface configured to forward the user data to        a cellular network for transmission to a user equipment (UE),    -   wherein the cellular network comprises a base station having a        radio interface and processing circuitry, the base station's        processing circuitry configured to perform any of the steps of        any of the Group B embodiments.

Embodiment D2: The communication system of the pervious embodimentfurther including the base station.

Embodiment D3: The communication system of the previous 2 embodiments,further including the UE, wherein the UE is configured to communicatewith the base station.

Embodiment D4: The communication system of the previous 3 embodiments,wherein:

-   -   the processing circuitry of the host computer is configured to        execute a host application, thereby providing the user data; and    -   the UE comprises processing circuitry configured to execute a        client application associated with the host application.

Embodiment D5: A method implemented in a communication system includinga host computer, a base station and a user equipment (UE), the methodcomprising:

-   -   at the host computer, providing user data; and    -   at the host computer, initiating a transmission carrying the        user data to the UE via a cellular network comprising the base        station, wherein the base station performs any of the steps of        any of the Group B embodiments.

Embodiment D6: The method of the previous embodiment, furthercomprising, at the base station, transmitting the user data.

Embodiment D7: The method of the previous 2 embodiments, wherein theuser data is provided at the host computer by executing a hostapplication, the method further comprising, at the UE, executing aclient application associated with the host application.

Embodiment D8: A user equipment (UE) configured to communicate with abase station, the UE comprising a radio interface and processingcircuitry configured to perform any of the previous 3 embodiments.

Embodiment D9: A communication system including a host computercomprising:

-   -   processing circuitry configured to provide user data; and    -   a communication interface configured to forward user data to a        cellular network for transmission to a user equipment (UE),    -   wherein the UE comprises a radio interface and processing        circuitry, the UE's components configured to perform any of the        steps of any of the Group A embodiments.

Embodiment D10: The communication system of the previous embodiment,wherein the cellular network further includes a base station configuredto communicate with the UE.

Embodiment D11: The communication system of the previous 2 embodiments,wherein:

-   -   the processing circuitry of the host computer is configured to        execute a host application, thereby providing the user data; and    -   the UE's processing circuitry is configured to execute a client        application associated with the host application.

Embodiment D12: A method implemented in a communication system includinga host computer, a base station and a user equipment (UE), the methodcomprising:

-   -   at the host computer, providing user data; and    -   at the host computer, initiating a transmission carrying the        user data to the UE via a cellular network comprising the base        station, wherein the UE performs any of the steps of any of the        Group A embodiments.

Embodiment D13: The method of the previous embodiment, furthercomprising at the UE, receiving the user data from the base station.

Embodiment D14: A communication system including a host computercomprising:

-   -   communication interface configured to receive user data        originating from a transmission from a user equipment (UE) to a        base station,    -   wherein the UE comprises a radio interface and processing        circuitry, the UE's processing circuitry configured to perform        any of the steps of any of the Group A embodiments.

Embodiment D15: The communication system of the previous embodiment,further including the UE.

Embodiment 16: The communication system of the previous 2 embodiments,further including the base station, wherein the base station comprises aradio interface configured to communicate with the UE and acommunication interface configured to forward to the host computer theuser data carried by a transmission from the UE to the base station.

Embodiment D17: The communication system of the previous 3 embodiments,wherein:

-   -   the processing circuitry of the host computer is configured to        execute a host application; and    -   the UE's processing circuitry is configured to execute a client        application associated with the host application, thereby        providing the user data.

Embodiment D18: The communication system of the previous 4 embodiments,wherein:

-   -   the processing circuitry of the host computer is configured to        execute a host application, thereby providing request data; and    -   the UE's processing circuitry is configured to execute a client        application associated with the host application, thereby        providing the user data in response to the request data.

Embodiment D19: A method implemented in a communication system includinga host computer, a base station and a user equipment (UE), the methodcomprising:

-   -   at the host computer, receiving user data transmitted to the        base station from the UE, wherein the UE performs any of the        steps of any of the Group A embodiments.

Embodiment D20: The method of the previous embodiment, furthercomprising, at the UE, providing the user data to the base station.

Embodiment D21: The method of the previous 2 embodiments, furthercomprising:

-   -   at the UE, executing a client application, thereby providing the        user data to be transmitted; and    -   at the host computer, executing a host application associated        with the client application.

Embodiment D22: The method of the previous 3 embodiments, furthercomprising:

-   -   at the UE, executing a client application; and    -   at the UE, receiving input data to the client application, the        input data being provided at the host computer by executing a        host application associated with the client application,    -   wherein the user data to be transmitted is provided by the        client application in response to the input data.

Embodiment D23: A communication system including a host computercomprising a communication interface configured to receive user dataoriginating from a transmission from a user equipment (UE) to a basestation, wherein the base station comprises a radio interface andprocessing circuitry, the base station's processing circuitry configuredto perform any of the steps of any of the Group B embodiments.

Embodiment D24: The communication system of the previous embodimentfurther including the base station.

Embodiment D25: The communication system of the previous 2 embodiments,further including the UE, wherein the UE is configured to communicatewith the base station.

Embodiment D26: The communication system of the previous 3 embodiments,wherein:

-   -   the processing circuitry of the host computer is configured to        execute a host application;    -   the UE is configured to execute a client application associated        with the host application, thereby providing the user data to be        received by the host computer.

Embodiment D27: A method implemented in a communication system includinga host computer, a base station and a user equipment (UE), the methodcomprising:

-   -   at the host computer, receiving, from the base station, user        data originating from a transmission which the base station has        received from the UE, wherein the UE performs any of the steps        of any of the Group A embodiments.

Embodiment D28: The method of the previous embodiment, furthercomprising at the base station, receiving the user data from the UE.

Embodiment D29: The method of the previous 2 embodiments, furthercomprising at the base station, initiating a transmission of thereceived user data to the host computer.

At least some of the following abbreviations may be used in thisdisclosure. If there is an inconsistency between abbreviations,preference should be given to how it is used above. If listed multipletimes below, the first listing should be preferred over any subsequentlisting(s).

-   -   2G Second Generation    -   3G Third Generation    -   3GPP Third Generation Partnership Project    -   4G Fourth Generation    -   5G Fifth Generation    -   5G-S-TMSI Fifth Generation System Architecture Evolution        Temporary Mobile Subscriber Identity    -   AC Alternating Current    -   ACK Acknowledgement    -   AP Access Point    -   AS Access Stratum    -   ASIC Application Specific Integrated Circuit    -   ATM Asynchronous Transfer Mode    -   BS Base Station    -   BSC Base Station Controller    -   BTS Base Transceiver Station    -   CA Carrier Aggregation    -   CD Compact Disk    -   CDMA Code Division Multiple Access    -   CN Core Network    -   COTS Commercial Off-the-Shelf    -   CPE Customer Premise Equipment    -   CPU Central Processing Unit    -   CRC Cyclic Redundancy Check    -   C-RNTI Cell Radio Network Temporary Identifier    -   CSI Channel State Information    -   D2D Device-to-Device    -   DAS Distributed Antenna System    -   DC Dual Connectivity    -   DCI Downlink Control Information    -   DFT Discrete Fourier Transform    -   DIMM Dual In-line Memory Module    -   DL Downlink    -   DRX Discontinuous Reception    -   DSP Digital Signal Processor    -   DVD Digital Video Disk    -   EEPROM Electrically Erasable Programmable Read Only Memory    -   eMTC Enhanced Machine Type Communication    -   eNB Evolved Node B    -   EPROM Erasable Programmable Read Only Memory    -   E-SMLC Evolved Serving Mobile Location Center    -   E-UTRAN Evolved Universal Mobile Telecommunications Service        Terrestrial Radio Access Network    -   FPGA Field Programmable Gate Array    -   GHz Gigahertz    -   gNB Fifth Generation Node B    -   GPS Global Positioning System    -   GSM Global System for Mobile Communications    -   HARQ Hybrid Automatic Repeat Request    -   HDDS Holographic Digital Data Storage    -   HD-DVD High Density Digital Versatile Disc    -   ID Identity    -   I/O Input and Output    -   IoT Internet of Things    -   IP Internet Protocol    -   I-RNTI Inactive Radio Network Temporary Identifier    -   kHz Kilohertz    -   LAN Local Area Network    -   LEE Laptop Embedded Equipment    -   LME Laptop Mounted Equipment    -   LTE Long Term Evolution    -   M2M Machine-to-Machine    -   MAC-I Message Authentication Code for Integrity    -   MANO Management and Orchestration    -   MCE Multi-Cell/Multicast Coordination Entity    -   MCG Master Cell Group    -   MDT Minimization of Drive Tests    -   MIMO Multiple Input Multiple Output    -   MME Mobility Management Entity    -   ms Millisecond    -   MSC Mobile Switching Center    -   MSR Multi-Standard Radio    -   MTC Machine Type Communication    -   NACK Negative Acknowledgement    -   NAS Non-Access Stratum    -   NB-IoT Narrowband Internet of Things    -   NCC nextHopChainingCount    -   NFV Network Function Virtualization    -   NG Next Generation    -   NIC Network Interface Controller    -   NR New Radio    -   O&M Operation and Maintenance    -   OFDM Orthogonal Frequency Division Multiplexing    -   OSS Operations Support System    -   OTT Over-the-Top    -   PBCH Physical Broadcast Channel    -   PCell Primary Cell    -   PCI Physical Cell Identity    -   PDA Personal Digital Assistant    -   PDCCH Physical Downlink Control Channel    -   PDCP Packet Data Convergence Protocol    -   PDSCH Physical Downlink Shared Channel    -   PLMN Public Land Mobile Network    -   PRB Physical Resource Block    -   PROM Programmable Read Only Memory    -   PSTN Public Switched Telephone Network    -   PUCCH Physical Uplink Control Channel    -   PUSCH Physical Uplink Shared Channel    -   QoS Quality of Service    -   RAID Redundant Array of Independent Disks    -   RAM Random Access Memory    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RB Resource Block    -   RF Radio Frequency    -   RNC Radio Network Controller    -   ROHC Robust Header Compression    -   ROM Read Only Memory    -   RRC Radio Resource Control    -   RRH Remote Radio Head    -   RRM Radio Resource Management    -   RRU Remote Radio Unit    -   RUIM Removable User Identity Module    -   SAE System Architecture Evolution    -   SCell Secondary Cell    -   SCG Secondary Cell Group    -   SDRAM Synchronous Dynamic Random Access Memory    -   SIM Subscriber Identity Module    -   SOC System on a Chip    -   SON Self-Organizing Network    -   SONET Synchronous Optical Networking    -   SpCell Special Cell    -   SPS Semi-Persistent Scheduling    -   SS Synchronization Signal    -   TCP Transmission Control Protocol    -   TMSI Temporary Mobile Subscriber Identity    -   UCI Uplink Control Information    -   UE User Equipment    -   UL Uplink    -   UMTS Universal Mobile Telecommunications Service    -   USB Universal Serial Bus    -   UTRAN Universal Terrestrial Radio Access Network    -   V2I Vehicle-to-Infrastructure    -   V2V Vehicle-to-Vehicle    -   V2X Vehicle-to-Everything    -   VMM Virtual Machine Monitor    -   VNE Virtual Network Element    -   VNF Virtual Network Function    -   VoIP Voice over Internet Protocol    -   WAN Wide Area Network    -   WCDMA Wideband Code Division Multiple Access    -   WD Wireless Device    -   WiMax Worldwide Interoperability for Microwave Access    -   WLAN Wireless Local Area Network

Those skilled in the art will recognize improvements and modificationsto the embodiments of the present disclosure. All such improvements andmodifications are considered within the scope of the concepts disclosedherein.

What is claimed is:
 1. A method, implemented by a User Equipment (UE) ornetwork node, the method comprising: exchanging Radio Resource Control(RRC) messaging between the UE and the network node, the RRC messagingcomprising: an RRC resume request message from the UE to the networknode; and an RRC connection release message comprising a suspendindication, wherein the RRC connection release message is from thenetwork node to the UE in response to the RRC resume request message;and replacing information in a stored Access Stratum (AS) context of theUE with new information comprised in the RRC connection release message,wherein replacing the information comprises replacing one or more of:stored security context information with security context informationcomprised in the RRC connection release message; a stored Inactive RadioNetwork Temporary Identifier (I-RNTI) with an I-RNTI comprised in theRRC connection release message; a stored cell identity with a cellidentity of a cell in which the UE sent the RRC resume request messageand received the RRC connection release message; a stored physical cellidentity with a physical cell identity of the cell in which the UE sentthe RRC resume request message and received the RRC connection releasemessage; or a stored Cell Radio Network Temporary Identifier (C-RNTI)with a C-RNTI obtained by the UE for the cell in which the UE sent theRRC resume request message and received the RRC connection releasemessage.
 2. The method of claim 1, wherein replacing the informationcomprises replacing: the stored cell identity with the cell identity ofthe cell in which the UE sent the RRC resume request message andreceived the RRC connection release message; the stored physical cellidentity with the physical cell identity of the cell in which the UEsent the RRC resume request message and received the RRC connectionrelease message; and the stored C-RNTI with the C-RNTI obtained by theUE for the cell in which the UE sent the RRC resume request message andreceived the RRC connection release message.
 3. The method of claim 1,wherein: replacing the information comprises replacing the storedsecurity context information with the security context informationcomprised in the RRC connection release message; and the securitycontext information comprises a next hop chaining count.
 4. The methodof claim 1, wherein replacing the information comprises replacing thestored I-RNTI with the I-RNTI comprised in the RRC connection releasemessage.
 5. The method of claim 1, wherein replacing the informationcomprises replacing the stored C-RNTI with the C-RNTI obtained by the UEfor the cell in which the UE sent the RRC resume request message andreceived the RRC connection release message.
 6. The method of claim 5,wherein the C-RNTI obtained by the UE for the cell in which the UE sentthe RRC resume request message and received the RRC connection releasemessage is a temporary C-RNTI.
 7. The method of claim 1, whereinreplacing the information comprises replacing the stored cell identitywith the cell identity of the cell in which the UE sent the RRC resumerequest message and received the RRC connection release message.
 8. Themethod of claim 1, wherein: replacing the information provides anupdated AS context of the UE; and the RRC messaging further comprises asubsequent RRC resume request that uses the updated AS context of theUE, wherein the subsequent RRC resume request is from the UE to thenetwork node.
 9. The method of claim 8, wherein the subsequent RRCresume request comprises a security integrity token derived from theupdated AS context of the UE.
 10. A network device, wherein the networkdevice is either a User Equipment (UE) or a network node, the networkdevice comprising: a radio interface; and processing circuitryassociated with the radio interface, wherein the processing circuitry isconfigured to cause the network device to: exchange Radio ResourceControl (RRC) messaging between the UE and the network node, the RRCmessaging comprising: an RRC resume request message from the UE to thenetwork node; and an RRC connection release message comprising a suspendindication, wherein the RRC connection release message is from thenetwork node to the UE in response to the RRC resume request message;and replace information in a stored Access Stratum (AS) context of theUE with new information comprised in the RRC connection release message,wherein to replace the information, the processing circuitry isconfigured to cause the network device to replace one or more of: storedsecurity context information with security context information comprisedin the RRC connection release message; a stored Inactive Radio NetworkTemporary Identifier (I-RNTI) with an I-RNTI comprised in the RRCconnection release message; a stored cell identity with a cell identityof a cell in which the UE sent the RRC resume request message andreceived the RRC connection release message; a stored physical cellidentity with a physical cell identity of the cell in which the UE sentthe RRC resume request message and received the RRC connection releasemessage; or a stored Cell Radio Network Temporary Identifier (C-RNTI)with a C-RNTI obtained by the UE for the cell in which the UE sent theRRC resume request message and received the RRC connection releasemessage.
 11. The network device of claim 10, wherein to replace theinformation in the stored AS context of the UE, the network device isconfigured to replace: the stored cell identity with the cell identityof the cell in which the UE sent the RRC resume request message andreceived the RRC connection release message; the stored physical cellidentity with the physical cell identity of the cell in which the UEsent the RRC resume request message and received the RRC connectionrelease message; and the stored C-RNTI with the C-RNTI obtained by theUE for the cell in which the UE sent the RRC resume request message andreceived the RRC connection release message.
 12. The network device ofclaim 10, wherein: to replace the information in the stored AS contextof the UE, the network device is configured to replace the storedsecurity context information with security context information comprisedin the RRC connection release message; and the security contextinformation comprises a next hop chaining count.
 13. The network deviceof claim 10, wherein to replace the information in the stored AS contextof the UE, the network device is configured to replace the stored I-RNTIwith the I-RNTI comprised in the RRC connection release message.
 14. Thenetwork device of claim 10, wherein to replace the information in thestored AS context of the UE, the network device is configured to replacethe stored C-RNTI with the C-RNTI obtained by the UE for the cell inwhich the UE sent the RRC resume request message and received the RRCconnection release message.
 15. The network device of claim 14, whereinthe C-RNTI obtained by the UE for the cell in which the UE sent the RRCresume request message and received the RRC connection release messageis a temporary C-RNTI.
 16. The network device of claim 10, wherein toreplace the information in the stored AS context of the UE, the networkdevice is configured to replace the stored cell identity with the cellidentity of the cell in which the UE sent the RRC resume request messageand received the RRC connection release message.
 17. The network deviceof claim 10, wherein: replacing the information provides an updated AScontext of the UE; and the RRC messaging further comprises a subsequentRRC resume request that uses the updated AS context of the UE, whereinthe subsequent RRC resume request is from the UE to the network node.18. The network device of claim 17, wherein the subsequent RRC resumerequest comprises a security integrity token derived from the updated AScontext of the UE.
 19. A non-transitory computer readable medium storinga computer program product for controlling a network device in awireless communication network, the network device being a UserEquipment (UE) or network node and the computer program productcomprising software instructions that, when run on the network device,cause the network device to: exchange Radio Resource Control (RRC)messaging between the UE and the network node, the RRC messagingcomprising: an RRC resume request message from the UE to the networknode; and an RRC connection release message comprising a suspendindication, wherein the RRC connection release message is from thenetwork node to the UE in response to the RRC resume request message;and replace information in a stored Access Stratum (AS) context of theUE with new information comprised in the RRC connection release message,wherein to replace the information the network device is caused toreplace one or more of: stored security context information withsecurity context information comprised in the RRC connection releasemessage; a stored Inactive Radio Network Temporary Identifier (I-RNTI)with an I-RNTI comprised in the RRC connection release message; a storedcell identity with a cell identity of a cell in which the UE sent theRRC resume request message and received the RRC connection releasemessage; a stored physical cell identity with a physical cell identityof the cell in which the UE sent the RRC resume request message andreceived the RRC connection release message; or a stored Cell RadioNetwork Temporary Identifier (C-RNTI) with a C-RNTI obtained by the UEfor the cell in which the UE sent the RRC resume request message andreceived the RRC connection release message.